[
https://issues.apache.org/jira/browse/HBASE-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728530#action_12728530
]
Jonathan Gray commented on HBASE-1622:
--------------------------------------
How would the KV know it's comparator? Needs to be lightweight.
Maybe we should have KeyValueComparable or something if we are going to end up
extending KV in otherwise unnecessary ways (or more importantly, ways that
might lead to misuse in other places). Would just extend KV and add Comparable
interface... we could even optionally pass in comparator on instantiation.
Might do the same for Result? I hate to add more classes, especially with long
names... just thinking.
> Make KeyValue implement the Comparable interface to make it work with
> Cascading.
> --------------------------------------------------------------------------------
>
> Key: HBASE-1622
> URL: https://issues.apache.org/jira/browse/HBASE-1622
> Project: Hadoop HBase
> Issue Type: New Feature
> Affects Versions: 0.20.0
> Reporter: Erik Holstad
> Assignee: Erik Holstad
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HBASE-1622-v1.patch, HBASE-1622-v2.patch
>
>
> As with making Result implement the Comparable interface, this is used for
> making HBase interact tightly with cascading, so that KeyValues can be put
> into Tuples.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
