Sorry Shashank I misunderstood your concern. Please ignore my previous message. To re-answer your question:
Yes, you're right, we do have this limitation now. Please open a JIRA ticket if you really wish it to be fixed: https://issues.apache.org/jira/browse/KYLIN thanks hongbin On Tue, Jul 21, 2015 at 4:45 PM, hongbin ma <[email protected]> wrote: > whether you use filters or not, you'll only use original Hive table > name/column name in your SQL query. The intermediate table and cube should > be transparent to end users. > > On Tue, Jul 21, 2015 at 4:13 PM, Shashank Prabhakara < > [email protected]> wrote: > >> Hi All, >> >> I need confirm that to use filters I have to use the alias defined in the >> SQL that will be created by Kylin for the flat table and not the table >> name. >> >> So that if I have a cube with Facts tabe 'facttable' and a lookup table >> 'products', and I want to select high priced products, I cannot use >> >> products.price > 50 >> mydb.products.price > 50 >> >> I am forced to use >> >> lookup_1.price > 50 >> >> And the number # on the lookup_# will depend on the order of the input. >> >> Since this is a Hive Query, I will be forced to use the alias without any >> workarounds?! >> >> Thanks in advance, >> Shashank >> > > > > -- > Regards, > > *Bin Mahone | 马洪宾* > Apache Kylin: http://kylin.io > Github: https://github.com/binmahone > -- Regards, *Bin Mahone | 马洪宾* Apache Kylin: http://kylin.io Github: https://github.com/binmahone
