Hi zhuoran, The cube size 700M is the serialized/compressed size on storage; In query time, Kylin need read and decompress dimension/measures into memory, the size will be larger than origin one; As HyperLogLog is much bigger than a normal measure (usually 1k to 64k each depends on the precision you select), its scan limit is much smaller than normal;
You're correct the threshold is computed from budget and the size of each line. If the cube is well designed, the run time scan/aggregation should be minor; To avoid such error/warning, you'd better analysis the query and optimize cube design. 2017-04-24 15:55 GMT+08:00 zhuoranlyu <[email protected]>: > BTW, if I set kylin.query.memory-budget-bytes to 6GB, there is no error > anymore. > > -- > View this message in context: http://apache-kylin.74782.x6. > nabble.com/A-problem-in-cube-size-tp7737p7752.html > Sent from the Apache Kylin mailing list archive at Nabble.com. > -- Best regards, Shaofeng Shi 史少锋
