hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-14989) Implementation of Mutation.getWriteToWAL() is backwards
Date Wed, 16 Dec 2015 02:36:46 GMT

     [ https://issues.apache.org/jira/browse/HBASE-14989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Taylor updated HBASE-14989:
---------------------------------
    Summary: Implementation of Mutation.getWriteToWAL() is backwards  (was: Mutation.getWriteToWAL
is backwards)

> Implementation of Mutation.getWriteToWAL() is backwards
> -------------------------------------------------------
>
>                 Key: HBASE-14989
>                 URL: https://issues.apache.org/jira/browse/HBASE-14989
>             Project: HBase
>          Issue Type: Bug
>            Reporter: James Taylor
>
> The implementation of the deprecated getWriteToWAL is backwards. It should return true
if this.durability == Durability.SYNC_WAL:
> {code}
> /**
>    * @deprecated Use {@link #getDurability()} instead.
>    * @return true if edits should be applied to WAL, false if not
>    */
>   @Deprecated
>   public boolean getWriteToWAL() {
>     return this.durability == Durability.SKIP_WAL;
>   }
> {code}
> For example, if mutation.durability is Durability.SYNC_WAL and the following code is
called {{clonedMutation.setWriteToWAL(mutation.getWriteToWAL())}}, it will disable writing
to the WAL for clonedMutation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message