[
https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302281#comment-15302281
]
James Taylor commented on PHOENIX-2903:
---------------------------------------
bq. In ScanUtil#setLocalIndexAttributes we need to replace
SCAN_ACTUAL_START_ROW with SCAN_START_ROW to set region start key as actual
start key
The SCAN_ACTUAL_START_ROW was renamed to SCAN_START_ROW and is set in all cases
(not just for local indexes) in BaseResultIterators.addNewScan(), which is the
code that collects up the scans to be run.
bq. Wonder all cases we set these values properly after split.
There's only one entry point in BaseResultIterators.getParallelScans(), as I
removed the other one which wasn't necessary (and wasn't correct either). Thus,
if the values were set in the original scan, they will also be set in the code
that runs when a split is detected.
> Handle split during scan for row key ordered aggregations
> ---------------------------------------------------------
>
> Key: PHOENIX-2903
> URL: https://issues.apache.org/jira/browse/PHOENIX-2903
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 4.8.0
>
> Attachments: PHOENIX-2903_v1.patch, PHOENIX-2903_v2.patch,
> PHOENIX-2903_v3.patch, PHOENIX-2903_wip.patch
>
>
> Currently a hole in our split detection code
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
