Kylin only supports star-schema; we don¹t suggest to use big lookup table, as that will downgrade the query performance;
If you do have such a table, you can try to join it into the fact table using hive view; For example, define a hive which joins the fact and customer into one; Then in Kylin create a cube which uses this view as fact, then you don¹t need this lookup table anymore; But please note your sql queries should be against the view. Just 2 cents from my side. On 11/8/15, 11:04 PM, "sdangi" <[email protected]> wrote: >Same here. One of the dim tables, coincidentally, CUSTOMER - has 1.8MM >rows. >Hitting the exact same issue. Earlier threads indicated, there is a >property [kylin.table.snapshot.max_mb] that needs to be overridden. >However, I'm unable to locate that. > >Thanks, >Regards, > > > >-- >View this message in context: >http://apache-kylin-incubating.74782.x6.nabble.com/dimension-table-limit-3 >00MB-tp2260p2274.html >Sent from the Apache Kylin (Incubating) mailing list archive at >Nabble.com.
