Can you grep logs like "to merge segment results" in that scenario?
cheney <[email protected]> 于2018年11月3日周六 下午4:15写道： > Thank your repling, .but I am sure there's only one OlapContext in the > quey in my scenario. > ---Original--- > *From:* "JiaTao Tao"<[email protected]> > *Date:* Sat, Nov 3, 2018 10:42 AM > *To:* "user"<[email protected]>; > *Subject:* Re: doubt about measure of processedRowCount > > Maybe count all the *valueA *would be more appropriate, cuz maybe there's > more than one OlapContext in the query ( one OlapContext correspond one > storageContext ). > > There are two good blogs about Kylin's query engine, you may take a look > :). > > https://blog.csdn.net/yu616568/article/details/50838504 > > https://zhuanlan.zhihu.com/p/30613434 > > cheney <[email protected]> 于2018年11月2日周五 下午11:10写道： > >> Hi, guys >> >> When I executed a sql in kylin, kylin server will log some log >> about query statics. for example, The log is as following: >> >> "Processed rows for each storageContext: *valueA*". *valueA *is >> processedRowCount. >> >> What I understand is processedRowCount is the record rows numbers >> returned by hbase. >> >> Hbase corprocessor will log region stats, including: "*Total >> scanned row*","Total filtered/aggred row". >> >> For one region, final records returned by hbase = *Total scanned >> row - *Total filtered/aggred row; >> Suppose this query need to scan 10 region in hbase, we can get >> every region stats. we can get all records *valueB *returned by hbase by >> suming every final records in 10 region. >> >> In general, *valueA *is equal to * valueB*, but *valueB *is much >> larger than *valueA* in sometimes. Why? >> >> >> > > > -- > > > Regards! > > Aron Tao > -- Regards! Aron Tao
