Hi Yubo, Thanks for the reporting and analysis; I'm trying to understand more; For case 1 and case 2 queries, are they using the same cube, or are you getting the result at the same moment?
The only didfference between case1 and case2 seems be the where condition: case1: where merchant_name like '%深海新创手机%' case2: where merchant_name like '%深海新创%' So the result set of case2 should be a superset of case1 (if they're using the same cube), but it isn't; Did I miss some key information? Thank you! 2016-08-10 10:53 GMT+08:00 [email protected] <[email protected]>: > CubeStorageQuery.search/ CubeSegmentScanner > > when filter is translated for the first segment, filter is changed to > CompareTupleFilter(IN clause) > translate will not triger for the next segments. > this is not right because dictionary is not same for every segments. > > assume data like this: > > merchant_name cube segment > 深海新创专营 20160725 > 深海新创手机 20160726 > > when search with like '%深海新创%' > CubeSegmentScanner scan segment '20160725' , and filter is changed to in > clause（ IN '深海新创专营'） > result is right for this segment ,but not for the next segments because > filter now has been changed. > > > > -- > View this message in context: http://apache-kylin.74782.x6. > nabble.com/Question-abount-BuildInFunctionTransformer-tp5499p5533.html > Sent from the Apache Kylin mailing list archive at Nabble.com. > -- Best regards, Shaofeng Shi
