Kylin today supports a very limited subset of SQL. In fact of the 100 TPC-DS queries we were able to execute only 10 queries. So a lot of SQL generated by Tableau will not be usable by Kylin.
On 1/8/16, 6:50 AM, "Luke Han" <[email protected]> wrote: >All SQL coming from Tableau are generated by Tableau. >Kylin's ODBC driver just a driver like other drivers which will be called >by Tableau when user drag & drop or make any other other actions. > >Please log JIRA when you facing any issue or such problem, we will look >into it and try to bring some test cases for further investment. > >Thanks. > > >Best Regards! >--------------------- > >Luke Han > >On Fri, Jan 8, 2016 at 1:08 PM, [email protected] <[email protected]> >wrote: > >> Dong, >> OKļ¼thanks. >> >> >> >> >> hua wang >> >> From: Dong Li >> Date: 2016-01-08 11:36 >> To: dev >> Subject: Re: A question about the sql generated by Tableau through Kylin >> ODBC >> Hello Hua, >> >> I'm sure we have no such logic in Kylin ODBC. In ODBC driver, we just >>pass >> user sql to Kylin rest server. >> To be more reasonable, maybe it should be tableau to decide whether to >>use >> IN or NOT IN? >> >> Thanks, >> Dong Li >> >> 2016-01-08 11:25 GMT+08:00 huawang <[email protected]>: >> >> > As "not in" filter is still a bug in Kylin's recent version, like 1.2, >> > while sometimes the sql generated by Tableau contains "not in". I have >> > inquried the engineer of Tableau, they said that the sql is mainly >> decided >> > by Kylin ODBC. >> > I want to known in which case will the sql contains "not in"? >> > thanks. >> >> >> >> >> -- >> Thanks, >> Dong >>
