@User Does that mean that we are moving all of our conversation to Apache workspace?

Or, do we want add another channel for users to get in touch with us?

Because we already have 200+ people in this workspace, I’m against of moving to a new workspace unless there’s a good incentive (e.g. workspace is paid version that they store all past conversation). I’m fine with adding an extra channel but committers should keep an eye on that channel not to miss the messages.

I prefer the latter

Multiple channels will be confusing, right?

Yes. Asf is not clear on the guidelines - should the channel be on ASF workspace or create project specific workspace. I am just opening this for discussion

Best would be to create a channel in asf and point folks to this workspace.

yeah in that case we can create a Pinot channel in ASF and pin the message to point our Slack workspace.

Hi Pinot Community, I’m preparing the upcoming release from current master branch commit (7cca1442d7ad41705643862b7237f445e8803368) as of date: Wed Feb 12 155831 PST 2020. Please let me know if you still have any changes wanted to get in by tomorrow Noon.

<!here> We are working on releasing pinot 1.0.0 and we have put together brand new getting started instructions to deploy Pinot, Presto with superset on Kubernetes... https://apache-pinot.gitbook.io/apache-pinot-cookbook/getting-started. Will be great if folks can give it a shot and provide feedback.

@User - Will upsert support will also be going in 1.0.0 ?

Not in 1.0.0. @User will probably have a better idea on when it will get merged into master.

@User is building 1.0.0 release as yet, I think he has not completed writing the release notes. Or, are you workinug with him to write the release notes? If you are, then please folllow the example in the 0.2.0 release notes, and come up with similar sections. There will be more on the incompat section. Does this answer your question @Isabi?

getting this error for this query:

Do we have deeper stack ?

Like what happened inside the constructor of InstanceResponseBlock

I guess that may need to be collected from server log…

Yes.. that would tell what exactly happened while building the data table for DISTINCT query response from the server

@User was this resolved? should we take it up on the mailing list?

still getting the same error but it is only with one table; same works for some other tables

looks like a bug when nothing matches the predicate

can you file an issue

but there are matching records with predicate in the query

If there are multiple servers, it is possible the one with exception has no match?

@User can you please file an issue

sure

just change the tableconfig and either restart servers or use admin api to reload segments

Will Pinot rebuild star-tree index in this case?

I think we have disabled it for star-tree