Gian Merlino

An update: we're planning to start doing PRs to set up the batch-query version of the feature in the near future. This batch-query version runs via the indexing service, and...

> Hi @gianm ! I recently started exploring Druid and was wondering if I could help with this issue. Please let me know, thanks! Hey @atris — I think one...

First PR (RPC): https://github.com/apache/druid/pull/12696

Next patch (frame format): https://github.com/apache/druid/pull/12745 @nishantmonu51 this is responsive to your question earlier! I thought about using Arrow, but didn't end up using it for a couple reasons: - We...

Even though the current work is focused on batch ingestion, I wanted to write down some thoughts about low-latency queries. I expect two pieces of the current work will be...

> Awesome. with this capability, we can do shuffle joins, window aggregations, etc without bottlenecking on the broker. have you also thought about elasticity? Right now, scaling historicals up and...

> I think these are both artifacts of not using async http handling so that we could manage the queue of query requests ourselves? I believe async http request handling...

> Sure, though that is probably an involved migration for current applications that use druid. The simplicity of the current API is attractive for interactive speed queries at least, so...

> The way we achieved these goals in other systems (Drill, Presto, Impala, Hive, etc.) is to use the classic optimizer + operator DAG architecture. The optimizer allows queries to...

Would be great. A few thoughts: 1. I think we'd want the option to be settable in query context. If we do this we'll also get a server-wide setting for...