[
https://issues.apache.org/jira/browse/HBASE-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635193#comment-14635193
]
Hudson commented on HBASE-13881:
--------------------------------
FAILURE: Integrated in HBase-1.2-IT #61 (See
[https://builds.apache.org/job/HBase-1.2-IT/61/])
HBASE-13881 Bug in HTable#incrementColumnValue implementation (Gabor Liptak)
(tedyu: rev 694600ae8942ed255716615881168779d7e8f917)
* hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Bug in HTable#incrementColumnValue implementation
> -------------------------------------------------
>
> Key: HBASE-13881
> URL: https://issues.apache.org/jira/browse/HBASE-13881
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.98.6.1, 1.0.1
> Reporter: Jerry Lam
> Assignee: Gabor Liptak
> Fix For: 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
>
> Attachments: HBASE-13881.branch-1.1.patch
>
>
> The exact method I'm talking about is:
> {code}
> @Deprecated
> @Override
> public long incrementColumnValue(final byte [] row, final byte [] family,
> final byte [] qualifier, final long amount, final boolean writeToWAL)
> throws IOException {
> return incrementColumnValue(row, family, qualifier, amount,
> writeToWAL? Durability.SKIP_WAL: Durability.USE_DEFAULT);
> }
> {code}
> Setting writeToWAL to true, Durability will be set to SKIP_WAL which does not
> make much sense unless the meaning of SKIP_WAL is negated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
