hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9142) Mutation#getFamilyMap() return type change between HBase 94 and 96 breaks downstream apps
Date Tue, 06 Aug 2013 22:57:47 GMT

     [ https://issues.apache.org/jira/browse/HBASE-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack updated HBASE-9142:
-------------------------

         Priority: Critical  (was: Major)
    Fix Version/s: 0.95.2
         Assignee: stack

Let me take a look...
                
> 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
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.95.2
>
>
> 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

Mime
View raw message