There were discussions about integrating with an alternative engine, like Impala, SparkSQL, etc; but no progress/action on that; If you already made some investigation or development, welcome to share and also contribute back to Kylin.
2017-03-18 1:13 GMT+08:00 Billy Liu <[email protected]>: > Thanks Sonny and Tianshuo. It makes sense. Currently, no one is working on > this still. It will be a great step to move Kylin to the next level. > > 2017-03-16 23:14 GMT-07:00 赵天烁 <[email protected]>: > >> great，we are trying to work on the same direction,which combine kylin and >> spark(not as cubing engine),drill is also a great choice I think. >> >> ------------------------------ >> >> 赵天烁 >> >> Kevin Zhao >> >> *[email protected] <[email protected]>* >> >> >> >> 珠海市魅族科技有限公司 >> >> MEIZU Technology Co., Ltd. >> >> 广东省珠海市科技创新海岸魅族科技楼 >> >> MEIZU Tech Bldg., Technology & Innovation Coast >> >> Zhuhai, 519085, Guangdong, China >> >> meizu.com >> >> >> *From:* Sonny Heer <[email protected]> >> *Date:* 2017-03-17 06:35 >> *To:* [email protected] >> *Subject:* Re: Drill integration ? >> The obvious one I can think of: Drill is a great ad hoc sql execution >> engine. In the case where kylin can't answer via cube, then direct the >> incoming query to drill. Both systems use calcite. The idea is to combine >> quick query response for most frequent queries (kylin predefined analytical >> queries) with more coverage (drill). (e.g. cases of no realization found >> or cross cube join)... >> >> On Thu, Mar 16, 2017 at 12:20 PM, Billy Liu <[email protected]> wrote: >> >>> Hi Heer, >>> >>> May I ask more more for this proposal, the benefits or use case? >>> >>> 2017-03-16 7:58 GMT-07:00 Sonny Heer <[email protected]>: >>> >>>> Is there any support for Apache Drill within Kylin? Any tickets for >>>> work done around this yet? >>>> >>>> Thanks >>>> >>>> >>> >> >> >> -- >> >> >> Pushpinder S. Heer >> Senior Software Engineer >> m: 360-434-4354 h: 509-884-2574 >> >> > -- Best regards, Shaofeng Shi 史少锋
