hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Lam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13881) Bugs in HTable incrementColumnValue implementation
Date Thu, 11 Jun 2015 15:07:01 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582038#comment-14582038
] 

Jerry Lam commented on HBASE-13881:
-----------------------------------

No I don't but I can create one. 

I believe the semantic of writeToWAL = true is equal to Durability.SYNC_WAL? Please confirm.

Thank you.

> Bugs 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
>
> 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)

Mime
View raw message