[
https://issues.apache.org/jira/browse/HBASE-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731407#comment-13731407
]
Hari Shreedharan commented on HBASE-9142:
-----------------------------------------
Yes, the new method will need to be renamed. We'd need to restore the old
method with the same signature to "unbreak" the downstream apps - but that
would break the new method as they both would differ only in return type. So
the new method would need to be renamed to something else like you suggested
above.
> 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
