take a look at kylin.storage.hbase.max-fuzzykey-scan in org.apache.kylin.common.KylinConfigBase#getQueryScanFuzzyKeyMax
2017-08-03 20:25 GMT+08:00 ShaoFeng Shi <shaofeng...@apache.org>: > It might be related with storage layer cache. You can make more tests to > see the differences. Besides, if you can provide more logs when executing > these two queries, that would be good for analysis. > > 在 2017年8月3日 下午4:26，wangzy24 <wangz...@163.com>写道： > > > 如下两个sql，差别是第二个hotel_code in的列表少一个元素（如红框标注），但性能差别很大: > > <http://apache-kylin.74782.x6.nabble.com/file/n8630/%E5%BE% > > AE%E4%BF%A1%E5%9B%BE%E7%89%87_20170803162007.png> > > <http://apache-kylin.74782.x6.nabble.com/file/n8630/%E5%BE% > > AE%E4%BF%A1%E5%9B%BE%E7%89%87_20170803162100.png> > > > > 个人觉得是in的元素过多，转换成rowkey比较多，导致kylin直接对表进行全部扫描，如果想不管rowkey多少， > > 始终想通过rowkey进行查询该如何做？ > > > > > > -- > > View this message in context: http://apache-kylin.74782.x6. > > nabble.com/sql-in-tp8630.html > > Sent from the Apache Kylin mailing list archive at Nabble.com. > > > > > > -- > Best regards, > > Shaofeng Shi 史少锋 > -- Regards, *Bin Mahone | 马洪宾*
