[
https://issues.apache.org/jira/browse/DRILL-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373933#comment-17373933
]
Cong Luo commented on DRILL-7962:
---------------------------------
[~paul-rogers] Hi. Is that the right way to process that (All the fragments
must be end)? I think the only reason might be that Drill wants to make per
query (included the LIMIT) return the same results (If the data sets are
unchanged).
> Stop query hbase region when other fragment have received more records than
> LIMIT records
> -----------------------------------------------------------------------------------------
>
> Key: DRILL-7962
> URL: https://issues.apache.org/jira/browse/DRILL-7962
> Project: Apache Drill
> Issue Type: Wish
> Components: Storage - HBase
> Affects Versions: 1.19.0
> Reporter: Hanoch Yang
> Priority: Blocker
>
> I find if one fragment have received records more than limit records, drill
> will not let other fragment cancel, but work unit received message, it will
> slow the query.
> case: what data i want locate in 2M region, but there is a 100M region and 2
> left 2M region. i use limit 10 to query. 4 fragement query 4 region, when one
> fragment get 10 record from 2M region, another 100M scanning fragment will
> not work. so all fragment must wait that fragment to finish scan, but it
> could have been unnecessary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
