[
https://issues.apache.org/jira/browse/PHOENIX-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated PHOENIX-2628:
---------------------------------------------
Attachment: PHOENIX-2628-wip.patch
[~jamestaylor]
Here just landing WIP patch handles NotServingRegionException when when there
are splits or merges. This is mostly applicable for local indexes and mostly
non aggregate queries. Aggregate queries work properly because we are using
region level locks for that.
With the earlier approach of prefixing the region start key to scan boundaries
may lead dataloss by skipping the second daughter region when there is split.
In the patch changing the scan boundaries to actual region boundaries and
adding scan suffix as attributes so that actual scan boundaries can be prepared
in the coprocessors.
And also using same logic of creating the iterators but only change is instead
of using scan from context passing new scan for which we need to create
iterators. We are always creating the iterators in TableResultIterator when we
recieve
The test case is still failing even though server returning proper results.
Looking at it.
Can you please review it. Thanks.
> Ensure split when iterating through results handled correctly
> -------------------------------------------------------------
>
> Key: PHOENIX-2628
> URL: https://issues.apache.org/jira/browse/PHOENIX-2628
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: Rajeshbabu Chintaguntla
> Attachments: PHOENIX-2628-wip.patch, PHOENIX-2628.patch
>
>
> We should start with a test case to ensure this works correctly, both for
> scans and aggregates.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
