[RESULT][VOTE] Release Apache Druid 27.0.0 [RC1]

Thanks to everyone who participated in the vote! The results are as follows: Abhishek Agarwal: +1 (binding) Karan Kumar: +1 (binding) Clint Wylie: +1 (binding) The vote has passed with 3 binding +1's. Thank you Amatya

Re: Spark Druid connectors, take 2

Hi all, First of all, thank you Julian for bringing this up and starting the conversation. Just to chime in on our (Netflix) use cases. We use Spark 3.3 and would benefit from both reader and writer. For the writer, we currently have a Spark job that writes data (from a Spark job) to an

Re: Spark Druid connectors, take 2

Looks like the “blue” fonts didn’t go through to the mailing list . However it is still tagged with [Rajiv]. * Rajiv From: Rajiv Mordani Date: Wednesday, August 9, 2023 at 2:14 PM To: dev@druid.apache.org Subject: Re: Spark Druid connectors, take 2 !! External Email Will, Julian,

Re: Spark Druid connectors, take 2

Will, Julian, See responses below tagged with [Rajiv] in blue: From: Will Xu Date: Tuesday, August 8, 2023 at 9:27 AM To: dev@druid.apache.org Subject: Re: Spark Druid connectors, take 2 !! External Email For which version to target, I think we should survey the Druid community

Re: Spark Druid connectors, take 2

Yes, it does make sense. For #2 (Spark reads Druid), I think Spark also needs to be able to get schema from Druid. This is probably a query to the broker. I wonder what's the UX look like for Spark SQL users on how they specify the schema. Would they create an EXTERNAL TABLE in Spark that maps to

Re: [VOTE] Release Apache Druid 27.0.0 [RC1]

+1 (binding) src: - verified LICENSE/NOTICE present - verified signature/checksum - RAT check passed - built binary distribution, ingested some data, ran some queries bin: - verified LICENSE/NOTICE present - verified signature/checksum - ingested some data, ran some queries docker: - verified

Re: Spark Druid connectors, take 2

For proper disclosure, it's been a while since I used Druid, but here's my 2 cents w.r.t Will's question (based on what I originally wrote in this design doc ): 1. *Spark writes to Druid*: 1. Based on