[
https://issues.apache.org/jira/browse/HBASE-9093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724933#comment-13724933
]
Lars Hofhansl commented on HBASE-9093:
--------------------------------------
I meant we cannot make forward changes. Guess my point was that 0.94 does
support the new API, and we should use the singularity to let us make API
incompatible changes.
So the issue in flume would be that the *older* 0.94 (and 0.92) versions cannot
be supported without reflection.
If that is major hassle, by all means lets keep the old API around, we just
have to weigh that against generally improving the API.
> 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.98.0, 0.95.2
>
> Attachments: HBASE-9093.patch, HBASE-9093.patch, HBASE-9093.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
