回复:答复: Should I remove this check about compare the last and fetched

2019-04-10 Thread yuzhang
check about compare the last and fetched Sure, here is the code at SortedIteratorMergerWithLimit.java:130. And the "Not sorted! last: XX fetched: XXX" exception may happen when query some table contain Chinese value(or messy code). ``` @Override public E next() { if (!nextFetc

答复: Should I remove this check about compare the last and fetched

2019-04-08 Thread Na Zhai
>应用 发件人: yuzhang 发送时间: Tuesday, March 26, 2019 11:27:14 PM 收件人: dev@kylin.apache.org 抄送: dev@kylin.apache.org 主题: Re: Should I remove this check about compare the last and fetched Sure, here is the code at SortedIteratorMergerWithLimit.java:130. And the "Not sorted! last: XXX

Re: Should I remove this check about compare the last and fetched

2019-03-26 Thread yuzhang
Sure, here is the code at SortedIteratorMergerWithLimit.java:130. And the "Not sorted! last: XX fetched: XXX" exception may happen when query some table contain Chinese value(or messy code). ``` @Override public E next() { if (!nextFetched) { throw new IllegalStateException("Should hasNe

Re: Should I remove this check about compare the last and fetched

2019-03-26 Thread elkan1788
I not sure can understand your question cleanly. Can you give more information about it, just like with a good sample. Also you can forward the code what you found and think that is happened! -- Sent from: http://apache-kylin.74782.x6.nabble.com/

Should I remove this check about compare the last and fetched

2019-03-26 Thread yuzhang
Hi team: When we use kylin, some queries over table contain Chinese value will throw "Not sorted! last: XX fetched: XXX" exception. Then, I found there is an check about compare last ITuple and fetched ITuple at SortedIteratorMergerWithLimit:130. But there also have an comment sa