You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/08/07 00:09:47 UTC

[jira] [Commented] (HBASE-9142) Mutation#getFamilyMap() return type change between HBase 94 and 96 breaks downstream apps

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

stack commented on HBASE-9142:
------------------------------

Could I restore the old call, deprecate it, and then make a new method named getFamilies w/ above signature?
                
> Mutation#getFamilyMap() return type change between HBase 94 and 96 breaks downstream apps
> -----------------------------------------------------------------------------------------
>
>                 Key: HBASE-9142
>                 URL: https://issues.apache.org/jira/browse/HBASE-9142
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>
> In Hbase-94, Mutation#getFamilyMap() had signature:
> public Map<byte[],List<KeyValue>> getFamilyMap()
> In Hbase-96 it is:
> public NavigableMap<byte[],List<? extends Cell>> getFamilyMap()
> I understand this might not be an easy fix or even a possible one - but it breaks downstream apps in a nasty way. If the app needs to process the individual columns, then the whole logic is now different. Is there a way to work around this, if this cannot be fixed?

--
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