[
https://issues.apache.org/jira/browse/HBASE-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733415#comment-13733415
]
Hadoop QA commented on HBASE-9142:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12596823/hbase-9142-0.95.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 18 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6654//console
This message is automatically generated.
> 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: Jonathan Hsieh
> Priority: Critical
> Fix For: 0.95.2
>
> Attachments: hbase-9142-0.95.patch, hbase-9142-trunk.patch
>
>
> 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
