1. "In this important scenario of realtime analytics, the reason here is that kylin has lag time due to model update of new segment build, is that correct?"
You are correct. 2. "If that is true, then can you suggest a work-around of combination of ... " Kylin is planning to introduce NRT streaming(coding is completed but not released), which can make the time-lag to about 3 minutes(that is my estimation but I am quite certain about it). NRT stands for 'near real-time', it will run a job and do micro-batch aggregation and persistence periodically. The price is that you need to run and monitor a long-running job. This feature is based on Spark Streaming, so you need knowledge of it. I am curious about what is the maximum time-lag your customers can tolerate? Personally, I guess minute level time-lag is ok for most cases. ------------------------ With warm regard Xiaoxiang Yu On Mon, Dec 4, 2023 at 12:28 PM Nam Đỗ Duy <na...@vnpay.vn.invalid> wrote: > Druid is better in > - Have a real-time datasource like Kafka etc. > > ========================== > > Hi Xiaoxiang, thank you for your response. > > In this important scenario of realtime alalytics, the reason here is that > kylin has lag time due to model update of new segment build, is that > correct? > > If that is true, then can you suggest a work-around of combination of : > > (time - lag kylin cube) + (realtime DB update) to provide > realtime capability ? > > IMO, the point here is to find that (realtime DB update) and integrate it > with (time - lag kylin cube). > > On Fri, Dec 1, 2023 at 1:53 PM Xiaoxiang Yu <x...@apache.org> wrote: > > > I researched and tested Druid two years ago(I don't know too much about > > the change of Druid in these two years. New features that I know are : > > new UI, fully on K8s etc). > > > > Here are some cases you should consider using Druid other than Kylin > > at the moment (using Kylin 5.0-beta to compare the Druid which I used two > > years ago): > > > > - Have a real-time datasource like Kafka etc. > > - Most queries are small(Based on my test result, I think Druid had > better > > response time for small queries two years ago.) > > - Don't know how to optimize Spark/Hadoop, want to use the K8S/public > > cloud platform as your deployment platform. > > > > But I do think there are many scenarios in which Kylin could be better, > > like: > > > > - Better performance for complex/big queries. Kylin can have a more > > exact-match/fine-grained > > Index for queries containing different `Group By dimensions`. > > - User-friendly UI for modeling. > > - Support 'Join' better? (Not sure at the moment) > > - ODBC driver for different BI.(its website did not show it supports ODBC > > well) > > - Looks like Kylin supports ANSI SQL better than Druid. > > > > > > I don't know Pinot, so I have nothing to say about it. > > Hope to help you, or you are free to share your opinion. > > > > ------------------------ > > With warm regard > > Xiaoxiang Yu > > > > > > > > On Fri, Dec 1, 2023 at 11:11 AM Nam Đỗ Duy <na...@vnpay.vn.invalid> > wrote: > > > >> Dear Xiaoxiang, > >> Sirs/Madams, > >> > >> May I post my boss's question: > >> > >> What are the pros and cons of the OLAP platform Kylin compared to Pinot > >> and > >> Druid? > >> > >> Please kindly let me know > >> > >> Thank you very much and best regards > >> > > >
