[
https://issues.apache.org/jira/browse/HBASE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733003#comment-13733003
]
Hudson commented on HBASE-9093:
-------------------------------
SUCCESS: Integrated in hbase-0.95-on-hadoop2 #223 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/223/])
HBASE-9093 HBase client API: Restore the writeToWAL method in 0.95 (Hari
Shreedharan)
Re-added to the 0.95 branch as deprecated methods. (jmhsieh: rev 1511337)
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Mutation.java
*
/hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestPutWriteToWal.java
REVERT "HBASE-9093 Hbase client API: Restore the writeToWal method"
The methods re-added to Mutation were misspelt. should be #setWriteToWAL and
#getWritetoWAL instead of #setWriteToWal and #getWriteToWal (jmhsieh: rev
1511336)
*
/hbase/branches/0.95/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Mutation.java
*
/hbase/branches/0.95/hbase-client/src/test/java/org/apache/hadoop/hbase/client/TestPutWriteToWal.java
> Hbase client API: Restore the writeToWal method
> -----------------------------------------------
>
> Key: HBASE-9093
> URL: https://issues.apache.org/jira/browse/HBASE-9093
> Project: HBase
> Issue Type: Bug
> Components: Client, Usability
> Affects Versions: 0.95.0
> Reporter: Hari Shreedharan
> Fix For: 0.95.2
>
> Attachments: HBASE-9093.patch, HBASE-9093.patch, HBASE-9093.patch,
> hbase-9093-v4.patch
>
>
> The writeToWal is used by downstream projects like Flume to disable writes to
> WAL to improve performance when durability is not strictly required. But
> renaming this method to setDurability forces us to use reflection to support
> hbase versions < 95 - which in turn hits performance, as this method needs to
> be called on every single write. I recommend adding the old method back as
> deprecated and removing it once hbase-95/96 becomes the popular version used
> in prod.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
