hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase
Date Tue, 26 Jun 2007 23:29:26 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508358
] 

Jim Kellerman commented on HADOOP-1519:
---------------------------------------

I am wondering why you needed to create the RecordWritable class. Couldn't you use ArrayWritable(KeyedData.class)
?

Also, in the future, it would be most beneficial if you could create a patch instead of sending
all the files. If you use eclipse, it is as simple as right click on the project -> Team
-> Create Patch...

Since you sent all the sources, I had to diff all the HBase files to find out that all you
had changed was HClient and that change was only the addition of the method getStartKeys.

> mapreduce input and output formats to go against hbase
> ------------------------------------------------------
>
>                 Key: HADOOP-1519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1519
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: contrib/hbase
>            Reporter: stack
>            Assignee: stack
>         Attachments: hbaseMR.tgz
>
>
> Inputs should allow specification of row range, columns and column versions.  Outputs
should allow specification of where to put the mapreduce result in hbase

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


Mime
View raw message