[
https://issues.apache.org/jira/browse/DRILL-7962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374295#comment-17374295
]
Charles Givre commented on DRILL-7962:
--------------------------------------
One other point I'd raise is that the HBase plugin doesn't seem to have a limit
pushdown. It does attempt to divide the query up amongst the fragments, but
after a cursory glance, it doesn't look like there is a limit pushdown. It
might be worthwhile to add that functionality as well so that the overall
fragment size is smaller.
> 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)
