[Discuss] Lookup table improvement: support global/big lookup table

Hi all, There are two limitations for current lookup table design: 1. lookup table size is limited, because table snapshot need to be cached in Kylin server, too large snapshot table will break Kylin server, also the snapshot building may take very long time when it is too large. 2. each segment

Re: What algorithm is the caching policy?

Kylin use ehcache as the cache solution, by default, it use LRU and timeToIdleSeconds is set to 1 day. All are configurable in ehcache.xml, by default it is: -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Re: Why 'is null' is not evaluable?

Yang wrote > Looks like a bug to me. > > On Thu, Apr 27, 2017 at 3:52 PM, magang > mg4work@ > wrote: > >> Hi, >> >> When sql contains filter: 'is null'/'is not null', the filter will not be >> push down to coprocessor, because the CompareTupleF

Why 'is null' is not evaluable?

Hi, When sql contains filter: 'is null'/'is not null', the filter will not be push down to coprocessor, because the CompareTupleFilter.isEvaluable() method return false, is it by design or just a bug? related code is here: