[
https://issues.apache.org/jira/browse/PHOENIX-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1313:
----------------------------------
Attachment: PHOENIX-1313_6.patch
A little closer with this patch, but the test seems to fail, but not in the
same spot everytime. Seems like a timing issue.
This patch only sets the EXPECTED_UPPER_REGION_KEY on the last scan in a
region, as this will prevent re-scanning the new region multiple times. I also
set the stopKey to the end key of the region containing the old
EXPECTED_UPPER_REGION_KEY, as we'll want to scan up to that new region
boundary. I think that's correct.
Thoughts?
> Investigate why LocalIndexIT.testLocalIndexScanAfterRegionSplit() is failing
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-1313
> URL: https://issues.apache.org/jira/browse/PHOENIX-1313
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2
> Reporter: James Taylor
> Assignee: rajeshbabu
> Fix For: 5.0.0, 4.2
>
> Attachments: PHOENIX-1313.patch, PHOENIX-1313_2.patch,
> PHOENIX-1313_4.patch, PHOENIX-1313_5.patch, PHOENIX-1313_6.patch
>
>
> I checked in a fairly big change
> (https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=d018cc1c6e01d9836de6e67af4f8b91de3269bfd)
> to improve encapsulation and fix a bunch of stats issues, and the following
> test started failing: LocalIndexIT.testLocalIndexScanAfterRegionSplit(). I
> tried to diagnose it, but that test is complicated. Would you mind taking a
> look [~rajesh23]?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
