Liran Funaro

Hi @jihoonson, @leventov, @gianm, @ebortnik, @b-slim, and @jon-wei. Since you had an interest in our previous discussions regarding `OakIncrementalIndex`, we wanted to update you that our new and improved implementation...

@jihoonson Thank you. We are eager to hear your valuable feedback.

@clintropolis We noticed your recent commits modified the same benchmarks as we did in this PR ([commit #a607c95](https://github.com/apache/druid/pull/10001/commits/a607c9565dafdca7614dcee2286a836b758d2a47)). Since you are familiar with this part of Druid, we will appreciate...

We noticed a lot of Druid users run their workload on Amazon EC2. We want to point out that this PR will not only improve performance but will also reduce...

Thanks to @yuanlihan for helping us find bugs on the realtime query side. Our system experiments focused on batch ingestion, so his contribution is highly appreciated.

Hi @jihoonson, have you had a chance to check out our issue/PR? We will be happy to answer any questions you might have.

### Updates We are working with our production teams at Verizon Media toward testing our incremental-index implementation on actual production data. As part of this effort, we discovered some issues...

We continue to evaluate Oak incremental-index on our (Yahoo) production workload and seeing interesting results. For example, we run Druid's middle-manager on two identical VMs that consumed events from the...

> i have merged your code in 0.18.1 branch，i am testing it @wangxiaobaidu11 I'm looking forward to hearing your results. If you need any help, please reach out.

Hi @a2l007, @jihoonson, @leventov, @gianm, @ebortnik, @b-slim, and @jon-wei. We approciate your support and the time you invested so far on this extention. After introducing a new extention-point in Druid...