You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/04/26 01:49:55 UTC

[jira] Created: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
--------------------------------------------------------------------------------

                 Key: HBASE-601
                 URL: https://issues.apache.org/jira/browse/HBASE-601
             Project: Hadoop HBase
          Issue Type: Improvement
            Reporter: stack
             Fix For: 0.2.0


HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.

Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-601:
------------------------

    Attachment: 601.patch

Removed test that no longer applies.  Removed deprecated methods from HTable.  Update BatchUpdate test.  Thrift will need fixing before 0.2 release what w/ all the API changes.

> Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-601
>                 URL: https://issues.apache.org/jira/browse/HBASE-601
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.2.0
>
>         Attachments: 601.patch
>
>
> HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.
> Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-601:
------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to TRUNK

> Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-601
>                 URL: https://issues.apache.org/jira/browse/HBASE-601
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.2.0
>
>         Attachments: 601.patch
>
>
> HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.
> Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-601:
---------------------------

    Assignee: stack

> Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-601
>                 URL: https://issues.apache.org/jira/browse/HBASE-601
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.2.0
>
>         Attachments: 601.patch
>
>
> HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.
> Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-601:
------------------------

    Status: Patch Available  (was: Open)

Make patch available so get reviewed.

> Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-601
>                 URL: https://issues.apache.org/jira/browse/HBASE-601
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.2.0
>
>         Attachments: 601.patch
>
>
> HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.
> Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HBASE-601) Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592723#action_12592723 ] 

Bryan Duxbury commented on HBASE-601:
-------------------------------------

+1

> Just remove deprecated methods in HTable; 0.2 is not backward compatible anyways
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-601
>                 URL: https://issues.apache.org/jira/browse/HBASE-601
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.2.0
>
>         Attachments: 601.patch
>
>
> HTable had deprecations introduce post 0.1 branch but 0.2 API is not going to be backward compatible because of other changes so I suggest we just remove the deprecated methods.  Users have to change their API anyways.  The less noisey the API, the easier it'll be on users figuring what to use instead.
> Added to 0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.