You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/04/12 04:23:25 UTC

[jira] [Created] (PHOENIX-2832) Ensure split handled correctly during aggregation over row key

James Taylor created PHOENIX-2832:
-------------------------------------

             Summary: Ensure split handled correctly during aggregation over row key
                 Key: PHOENIX-2832
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2832
             Project: Phoenix
          Issue Type: Bug
            Reporter: James Taylor
            Assignee: James Taylor


Related to PHOENIX-2628, but specifically for an "ordered" aggregation (i.e. an aggregation over leading row key columns). We should be able to this by catching the StaleRegionBoundaryCacheException in GroupedAggregatingResultIterator (or in potentially a new class once PHOENIX-2818 is implemented) and then starting the scan from the current key returned. This will work because a row would not yet have been returned to the client and we'd just re-calculate the state for the current row being aggregated and move on from there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)