[
https://issues.apache.org/jira/browse/HBASE-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728782#action_12728782
]
Erik Holstad commented on HBASE-1622:
-------------------------------------
When it comes down to the use in Cascading I don't think that these things will
be a problem, but if people are using the Comparable in other places and for
catalog keys, this will cause confusion. I guess one use case would be to put
KeyValues in a map and not specify a comparator.
Not a big fan of Adding more classes either, but maybe we can put them in the
mapreduce package or a Cascading package so we have them only where they should
be used, to avoid miss use of these new classes too, and strap some warnings in
the top.
> 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.
