[
https://issues.apache.org/jira/browse/PHOENIX-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17724105#comment-17724105
]
Jacob Isaac commented on PHOENIX-6910:
--------------------------------------
Hi [~stoty]
I think you are addressing the same issue that I thought was the root cause -
intersectScan method does not take into account that the region boundaries
could have changed (for e.g example after a merge).
This was my initial PR, but I ran into some test failures with this PR and then
got sidetracked.
I ran the IT tests
SaltingWithRegionMergeIT
in this patch [^0001-PHOENIX-6910-initial-commit.patch] against your PR and was
getting similar test failures.
Hope this helps.
> 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: Istvan Toth
> Priority: Major
> Attachments: 0001-PHOENIX-6910-initial-commit.patch
>
>
> 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)
