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

Istvan Toth commented on PHOENIX-6910:
--------------------------------------

This is where we set wrong end key for the scan range, by assuming that the 
region (guidepost ?) has only one key:
https://github.com/apache/phoenix/blob/a0abd7198a694ae4405287da8ba14517b9537392/phoenix-core/src/main/java/org/apache/phoenix/compile/ScanRanges.java#L393

> Scans created during query compilation and execution against salted tables 
> need to be more resilient
> ----------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6910
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6910
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.1.3
>            Reporter: Jacob Isaac
>            Assignee: Jacob Isaac
>            Priority: Major
>
> The Scan objects created during where compilation and execution phases are 
> incorrect when salted tables are involved and their regions have moved. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to