[
https://issues.apache.org/jira/browse/HBASE-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-17167:
------------------------------
Attachment: HBASE-17167-v2.patch
Revert the clone of scan object. Modify several UTs to remove the reusing of
scan object. But I think it is impossible to prevent user reusing the scan
object, that't why we add a comment to tell user the start key may be changed.
But it is not a good idea to tell user the mvcc read point is changed and you
need to reset it as the methods are marked as private. So finally I decided to
reset the mvcc read point in getScanner.
> Pass mvcc to client when scan
> -----------------------------
>
> Key: HBASE-17167
> URL: https://issues.apache.org/jira/browse/HBASE-17167
> Project: HBase
> Issue Type: Sub-task
> Components: Client, scan
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0, 1.4.0
>
> Attachments: HBASE-17167-v1.patch, HBASE-17167-v2.patch,
> HBASE-17167.patch
>
>
> For the current implementation, if we use batch or allowPartial when scan,
> then the row level atomic can not be guaranteed if we need to restart a scan
> in the middle of a record due to region move or something else.
> We can return the mvcc used to open scanner to client and client could use
> this mvcc to restart a scan to get row level atomic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
