[ 
https://issues.apache.org/jira/browse/HBASE-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074903#comment-16074903
 ] 

Josh Elser commented on HBASE-18241:
------------------------------------

bq. Is it valid to change the Client API in a source compatible way for a major 
version

If memory serves... I think you would need to leave 
{{Admin#createTable(HTableDescriptor)}}, deprecate it, and then add the new API 
{{Admin#createTable(TableDescriptor)}}.

If you removed the method completely, when clients upgrade from 1.x to 2.x, 
their code would not directly work. The intent of semver for this circumstance 
is that users code would still work from 1.x to 2.x, but is not guaranteed to 
work for 3.x.

> Change client.Table, client.Admin, Region, and Store to not use 
> HTableDescriptor or HColumnDescriptor
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-18241
>                 URL: https://issues.apache.org/jira/browse/HBASE-18241
>             Project: HBase
>          Issue Type: Task
>          Components: Client
>            Reporter: Biju Nair
>            Assignee: Chia-Ping Tsai
>            Priority: Critical
>             Fix For: 3.0.0, 2.0.0-alpha-2
>
>         Attachments: HBASE-18241.v0.patch, HBASE-18241.v1.patch, 
> HBASE-18241.v2.patch, HBASE-18241.v2.patch, HBASE-18241.v3.patch, 
> HBASE-18241.v3.patch, HBASE-18241.v4.patch
>
>
> {{HTableDescriptor}} is deprecated and scheduled to be removed in 3.0. But 
> [client.Table|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Table.java#L69]
>  and 
> [client.Admin|https://github.com/apache/hbase/blob/a66d491892514fd4a188d6ca87d6260d8ae46184/hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java#L198]
>  method {{getTableDescriptor}} returns {{HTableDescriptor}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to