[ 
https://issues.apache.org/jira/browse/PHOENIX-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298428#comment-15298428
 ] 

Rajeshbabu Chintaguntla commented on PHOENIX-2903:
--------------------------------------------------

I think when we setup local index scan at server we need to make use of it 
instead of SCAN_START_ROW_SUFFIX then if it's not null otherwise we go through 
already scanned data.
{noformat}
    private static void setupLocalIndexScan(Scan scan, HRegionInfo regionInfo) {
534             final byte[] lowerInclusiveRegionKey = regionInfo.getStartKey();
535             final byte[] upperExclusiveRegionKey = regionInfo.getEndKey();
536             byte[] prefix = lowerInclusiveRegionKey.length == 0 ? new 
byte[upperExclusiveRegionKey.length]: lowerInclusiveRegionKey;
537             int prefixLength = lowerInclusiveRegionKey.length == 0? 
upperExclusiveRegionKey.length: lowerInclusiveRegionKey.length;
538             if(scan.getAttribute(SCAN_START_ROW_SUFFIX)!=null) {
539                 
scan.setStartRow(ScanRanges.prefixKey(scan.getAttribute(SCAN_START_ROW_SUFFIX), 
0, prefix, prefixLength));
540             }
541             if(scan.getAttribute(SCAN_STOP_ROW_SUFFIX)!=null) {
542                 
scan.setStopRow(ScanRanges.prefixKey(scan.getAttribute(SCAN_STOP_ROW_SUFFIX), 
0, prefix, prefixLength));
543             }
544         }
{noformat}

> 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)

Reply via email to