[jira] [Resolved] (HBASE-13983) Doc how the oddball HTable methods getStartKey, getEndKey, etc. will be removed in 2.0.0

["stack (JIRA)" <ji...@apache.org>]

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

stack resolved HBASE-13983.
---------------------------
       Resolution: Fixed
     Hadoop Flags: Incompatible change,Reviewed
    Fix Version/s: 1.1.2
                   1.2.0
                   1.0.2
                   2.0.0
     Release Note: 
Adds extra doc on getStartKeys, getEndKeys, and getStartEndKeys in HTable explaining that they will be removed in 2.0.0 (these methods did not get the proper full major version deprecation cycle).

In this issue, we actually also remove these methods in master/2.0.0 branch.

Thanks for reviews lads (Fixed the issue you fingered in opening comment [~anoop.hbase] -- thanks... and moved this as subissue as you suggested [~mantonov])

> Doc how the oddball HTable methods getStartKey, getEndKey, etc. will be removed in 2.0.0
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-13983
>                 URL: https://issues.apache.org/jira/browse/HBASE-13983
>             Project: HBase
>          Issue Type: Sub-task
>          Components: documentation
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
>             Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2
>
>         Attachments: 13983.branch-1.txt, 13983.txt
>
>
> See the mail thread on dev "Semantic Versioning Worksheet" for background discussion. A few methods in HTable were NOT deprecated when we cut 1.0.0: getStartKeys, getEndKeys.... This issue is about doc'ing that even though they were not deprecated, they will be removed in hbase 2.0.0.



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