[
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_5.patch
I made the changes you recommended, [~rajesh23] (see attached patch), but the
tests still don't pass. I don't understand by (1) would be necessary. It might
lead to duplicates, because there may be multiple parallel scans that were done
on that region and we're extending the stop key for all of them. What's wrong
with using the original stop key from the scan that failed? The code will reset
the EXPECTED_UPPER_REGION_KEY based on the new region boundaries.
> 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
>
>
> 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)
