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

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 0.95.2
• Hadoop Flags: Reviewed

Release Note

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

For 0.95/0.96, we need to preserve the getFamilyMap signature through a deprecation cycle. The new
method needs to be present alongside the old in 0.95, so we rename the method with the new signature
to getFamilyCellMap() in both trunk and 0.95, and restore a deprecated version of the old in 0.95.

• Assignee: Jonathan Hsieh
• Reporter: Hari Shreedharan
• Created: 06/Aug/13 20:20
• Updated: 23/Sep/13 19:22
• Resolved: 08/Aug/13 23:52

Description

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?