[
https://issues.apache.org/jira/browse/HBASE-10467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892470#comment-13892470
]
Enis Soztutar commented on HBASE-10467:
---------------------------------------
bq. So when we make some API deprecated in one version, when we can remove
this? I was thinking that we can remove it in next major version. I am also
having the same feeling as what Lars said above. Pls correct if I am wrong.
We had deprecated stuff removed from 0.98, but we decided to add some of them
back so that some important clients (like Pig and Hive) does not have to have a
shim layer to be able to compile both with 0.94, 0.96 and 0.98. It is a
convenience we are providing for the downstreamers to make their life easier I
think. See HBASE-10368 and HBASE-10339. The main argument is that, as long as
0.94 is around, downstreamers will want to be able to compile with 0.94 and
0.96,0.98, and 1.0 at the same time. I am fine with dropping the API's in 1.0,
as long as we are not causing a lot of disruption to our consumers.
bq. Reverted patch v3 from trunk.
HTD.isDeferredLogFlush() was replaced with setDurability(), and the method was
deprecated. We should remove the new methods isAsyncLogFlush() altogether.
> Restore HTableDescriptor#isDeferredLogFlush()
> ---------------------------------------------
>
> Key: HBASE-10467
> URL: https://issues.apache.org/jira/browse/HBASE-10467
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.98.0
>
> Attachments: 10467-v2.txt, 10467-v3.txt, 10467.txt
>
>
> HTableDescriptor#isDeferredLogFlush() should be restored in 0.98 and marked
> Deprecated.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
