[
https://issues.apache.org/jira/browse/KYLIN-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15896844#comment-15896844
]
hongbin ma commented on KYLIN-2483:
-----------------------------------
just gave it another thought, disabling SortedIteratorMergerWithLimit with
limit push down enabled will return wrong results. Since it's always tempting
to enable limit push down, we'll have to suffer the cost of
SortedIteratorMergerWithLimit.
> SortedIteratorMergerWithLimit could be slower when number of total merge rows
> is small
> --------------------------------------------------------------------------------------
>
> Key: KYLIN-2483
> URL: https://issues.apache.org/jira/browse/KYLIN-2483
> Project: Kylin
> Issue Type: Improvement
> Reporter: hongbin ma
> Assignee: hongbin ma
>
> if the pushed down limit is small enough (say less than 100),
> SortedIteratorMergerWithLimit will bring RELATIVELY significant costs. I'm
> adding a new configuration entry called
> kylin.query.merge-sort-partition-results.min-limit (default 100) to fix this
> issue
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
