You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Erik Holstad (JIRA)" <ji...@apache.org> on 2009/08/13 23:51:14 UTC

[jira] Resolved: (HBASE-1617) Make Result comparable to work with Cascading

     [ https://issues.apache.org/jira/browse/HBASE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Erik Holstad resolved HBASE-1617.
---------------------------------

    Resolution: Fixed

This feature is not needed any more. Cascading is going to change its requirements so that you supply it with a comparator in the cases where that is needed, so that a regular input to a Cascading Tuple doesn't have to be Comparable any more. 

> Make Result comparable to work with Cascading
> ---------------------------------------------
>
>                 Key: HBASE-1617
>                 URL: https://issues.apache.org/jira/browse/HBASE-1617
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: client
>    Affects Versions: 0.20.0
>            Reporter: Erik Holstad
>            Assignee: Erik Holstad
>         Attachments: HBASE-1617-v1.patch, HBASE-1617-v2.patch
>
>
> When using HBase as a Tap for Cascading it makes sense to put the result from HBase into a Tuple. The Element in the tuple needs to be comparable.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.