[
https://issues.apache.org/jira/browse/PHOENIX-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7728:
---------------------------------
Description:
I have found during the HBase 3.0 support work that it makes assumptions about
Hbase behaviour which are not true in HBase 3.
It is also
* unneccessarily complex,
* uses the first row of the result list as lastReturnedRowKey, which seems to
be a bug
* consumes dummy results, which may result in not returning in the desired time
limit.
was:
I have found during the HBase 3.0 support work that it makes assumptions about
Hbase behaviour which are not true in HBase 3.
It is also
* unneccessary complex,
* uses the first row of the result list as lastReturnedRowKey, which seems to
be a bug
* consumes dummy results, which may result in not returning in the desired time
limit.
> Fix skipValidRowsSent logic in
> GroupedAggregateRegionObserver.UnorderedGroupByRegionScanner
> -------------------------------------------------------------------------------------------
>
> Key: PHOENIX-7728
> URL: https://issues.apache.org/jira/browse/PHOENIX-7728
> Project: Phoenix
> Issue Type: Bug
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> I have found during the HBase 3.0 support work that it makes assumptions
> about Hbase behaviour which are not true in HBase 3.
> It is also
> * unneccessarily complex,
> * uses the first row of the result list as lastReturnedRowKey, which seems
> to be a bug
> * consumes dummy results, which may result in not returning in the desired
> time limit.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
