You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (JIRA)" <ji...@apache.org> on 2016/01/14 06:53:39 UTC
[jira] [Updated] (HBASE-14989) Implementation of
Mutation.getWriteToWAL() is backwards
[ https://issues.apache.org/jira/browse/HBASE-14989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk updated HBASE-14989:
---------------------------------
Fix Version/s: (was: 1.1.4)
1.1.3
> Implementation of Mutation.getWriteToWAL() is backwards
> -------------------------------------------------------
>
> Key: HBASE-14989
> URL: https://issues.apache.org/jira/browse/HBASE-14989
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: James Taylor
> Assignee: Enis Soztutar
> Fix For: 1.2.0, 1.3.0, 1.1.3, 0.98.17, 1.0.4
>
> Attachments: HBASE-14989.1.branch-1.patch, hbase-14989-branch-1_v1.patch
>
>
> 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)