[
https://issues.apache.org/jira/browse/HBASE-16768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15547982#comment-15547982
]
ramkrishna.s.vasudevan commented on HBASE-16768:
------------------------------------------------
bq.But it should be cheaper for getting seqID, the method just returns a long
value.
Yes I can see that.
But better to avoid still because in one of our internal changes we were seeing
if we can add a Cell that does append the seqid in the backing byte[] itself.
In that case it could be costly to parse it from the cell every time. But that
is not there now in trunk anyway.
> Inconsistent results from the Append/Increment
> ----------------------------------------------
>
> Key: HBASE-16768
> URL: https://issues.apache.org/jira/browse/HBASE-16768
> Project: HBase
> Issue Type: Bug
> Reporter: ChiaPing Tsai
> Priority: Minor
> Attachments: HBASE-16768.v0.patch
>
>
> If the Append/Increment skips the WAL, the sequential id will not be updated.
> It introduces that the AbstractMemStore#upsert may remove the cell even
> though the cell is visible to the oldest scanner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
