[
https://issues.apache.org/jira/browse/HBASE-13836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578649#comment-14578649
]
ramkrishna.s.vasudevan commented on HBASE-13836:
------------------------------------------------
{code}
public static final byte[] SKIP_RESET_SEQ_ID =
Bytes.toBytes("SKIP_RESET_SEQ_ID");
{code}
May be you can add the reason and specify used in MOB cases. It will help to
understand later because it is specific to MOB.
Also you can always make this 'true' and avoid the setSkipResetSeqId(true)
every time for a non-bulk load case? If is a bulk load you can set based on the
metadata info.
{code}
private boolean skipResetSeqId = false;
{code}
> Do not reset the mvcc for bulk loaded mob reference cells in reading
> --------------------------------------------------------------------
>
> Key: HBASE-13836
> URL: https://issues.apache.org/jira/browse/HBASE-13836
> Project: HBase
> Issue Type: Sub-task
> Components: mob
> Affects Versions: hbase-11339
> Reporter: Jingcheng Du
> Assignee: Jingcheng Du
> Fix For: hbase-11339
>
> Attachments: HBASE-13836.diff
>
>
> Now in scanner, the cells mvcc of the bulk loaded files are reset by the
> seqId parsed from the file name. We need to skip this if the hfiles are
> bulkloaded in mob compactions.
> In mob compaction, the bulk loaded ref cell might not be the latest cell
> among the ones that have the same row key. In reading, the mvcc is reset by
> the largest one, it will cover the real latest ref cell. We have to skip the
> resetting in this case.
> The solution is we add a new field to fileinfo, when this field is set as
> true, we skip the resetting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
