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 Sat, 30 Jun 2007 10:19:04 GMT

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

Jim Kellerman commented on HADOOP-1519:


Michael (Stack) and I decided to do what you suggest. We also made a
couple of other minor changes. No big deal, we are almost ready to
commit, as soon as we can get the test we wrote (based on your example)
to run under Hudson (it does run in our environment - but seems to run
out of retries or times out before it can run in the build environment).

Thanks for your contribution here. It saved us quite a bit of work.


Jim Kellerman, Senior Engineer; Powerset

> 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
>    Affects Versions: 0.14.0
>            Reporter: stack
>            Assignee: Jim Kellerman
>             Fix For: 0.14.0
>         Attachments: hbaseMR.tgz, patch.txt, patch.txt, patch.txt, patch.txt, patch.txt
> 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.

View raw message