You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jianwei Cui (JIRA)" <ji...@apache.org> on 2016/03/21 14:10:25 UTC
[jira] [Created] (HBASE-15497) Incorrect javadoc for atomicity
guarantee of Increment and Append
Jianwei Cui created HBASE-15497:
-----------------------------------
Summary: Incorrect javadoc for atomicity guarantee of Increment and Append
Key: HBASE-15497
URL: https://issues.apache.org/jira/browse/HBASE-15497
Project: HBase
Issue Type: Bug
Components: documentation
Affects Versions: 2.0.0
Reporter: Jianwei Cui
Priority: Minor
At the front of {{Increment.java}} file, there is comment about read atomicity:
{code}
* This operation does not appear atomic to readers. Increments are done
* under a single row lock, so write operations to a row are synchronized, but
* readers do not take row locks so get and scan operations can see this
* operation partially completed.
{code}
It seems this comment is not true after MVCC integrated [HBASE-4583|https://issues.apache.org/jira/browse/HBASE-4583]. Currently, the readers can be guaranteed to read the whole result of Increment if I am not wrong. Similar comments also exist in {{Append.java}}, {{Table#append(...)}} and {{Table#increment(...)}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)