hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9496) make sure HBase APIs are compatible between 0.94 and 0.96
Date Wed, 11 Sep 2013 21:54:52 GMT

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

stack commented on HBASE-9496:

Patch is good.  I question the Result change.  Where on client side do we make Results?  In
mapreduce?  Do we need to change the constructor so KV?

On CPs, yeah, we probably can argue we have a pass.

Let me take a look at REST and Thrifts.  Do we let Cell out via their APIs?

I think Jon did filters already.
> make sure HBase APIs are compatible between 0.94 and 0.96
> ---------------------------------------------------------
>                 Key: HBASE-9496
>                 URL: https://issues.apache.org/jira/browse/HBASE-9496
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Blocker
>             Fix For: 0.96.0
>         Attachments: HBASE-9496-v0-96.patch
> Follow-up for HBASE-9477.
> Some other methods are now different between 94 and 96 (Result::getColumnLatest, Put::get,
anything that takes a collection of Cell, e.g. Result ctor, Mutation::setFamilyMap etc.).
> I am assuming things that accept Cell (Increment::add, Delete::addDeleteMarker) don't
need to change.

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

View raw message