[
https://issues.apache.org/jira/browse/HBASE-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728850#action_12728850
]
Erik Holstad commented on HBASE-1622:
-------------------------------------
For the Cascading use case I really don't think it will be that much of an
issue, since most data processed is not taken from those tables, but it might
be confusing for users that might start using these properties in some other
context, where it will cause more trouble.
thinking about it some more, I don't think that it is a really bad option to
add these to classes to the mapreduce package and not pollute KeyValue with
more stuff.
What do you think?
> 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.
