The SQL overhead is around hundreds of ms, so don't worry about the ms level difference.
I'm more interested in the HBase/ES comparison on big data load. HBase design incorporates random read/write, while ES can optimize for batch load and read-only. In that sense, HBase is born with a small burden. Many have suggested storage other than HBase. Here we have another one ES. :-) I think that's what Kylin has plugin architecture. Anyone can implement a new storage plugin and run Kylin on anywhere if not HBase. On Mon, Nov 16, 2015 at 2:31 PM, Sarnath <[email protected]> wrote: > On Nov 16, 2015 5:07 AM, "Luke Han" <[email protected]> wrote: > > > > Hi Sarnath, It's interesting result, could you please share your full > testing case, data and result? > > Thanks. I will post the result this week. Will need to cross check > > > And could you please share your cube engine's design even code(is it open > source?)? So that we also could know how the comparison goes to and help > you to understand more. Thanks. > > This is closed software. But we don't do any smart stuff. Rather straight > forward...thanks! > > > > Regards! > > Luke Han > > > > _____________________________ > > From: Sarnath <[email protected]> > > Sent: 星期一, 十一月 16, 2015 01:06 > > Subject: Re: Group by + where clause > > To: <[email protected]> > > > > > > A small correction: I meant data block encoding on hbase >
