[jira] Created: (HADOOP-1519) mapreduce input and output formats to go against hbase

classic Classic list List threaded Threaded
32 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
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


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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

    Attachment: hbaseMR.tgz

Contributed by Vuk Ercegovac. Will require some examination as it includes changes to some of the core Hadoop classes

> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

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

Vuk,

Many of the HBase sources are different from the trunk revision. Can you provide a list of the files you needed to change to support Map/Reduce?

> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

    [ 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman reassigned HADOOP-1519:
-------------------------------------

    Assignee: Jim Kellerman  (was: stack)

> 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: Jim Kellerman
>         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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

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

Vuk,

It would be really nice if you could provide a self contained test case for this code. What you have is good, but I have no way to verify that it is working the way that you expect.

Thanks.

> 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: Jim Kellerman
>         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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Vuk Ercegovac updated HADOOP-1519:
----------------------------------

    Attachment: patch.txt

Patch for map/reduce to work with hbase.

> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Vuk Ercegovac commented on HADOOP-1519:
---------------------------------------

Thanks for the feedback and apologies for the initial tgz file. Let me know if the patch works for you.

I included a sample driver, org.apache.hadoop.mapred.TableJobExample, that scans an input table's columns and writes to an output table. The input/output tables along with the columns to scan are user specified. Filtering can be done by extending TableMap. Specifying a row range and versions are good suggestions.

I tried ArrayWritable but ran into the following problem at line 444 of MapTask.java. Value is instantiated
with the given class, say ArrayWritable, using its empty constructor. Then in line 459, value.readFields
is called. At this point, the valueClass in ArrayWritable is null, since it was not instantiated or set appropriately. However, ArrayWritable assumes that it is set, rather than reading it off the stream. My workaround is through RecordWritable but am certainly open to better suggestions.

I have tried this code using MiniHBaseCluster and on a distributed cluster (thanks for the new start/stop scripts!) for the simple example of copying tables.

> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

udanax commented on HADOOP-1519:
--------------------------------

Useful for me.

> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

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

Vuk,

Thanks for the explanation about ArrayWritable, makes perfect sense now. Also thanks for the extra effort creating the patch, etc. Very much appreciated.

I just need to do a bit of testing, etc and then I'll commit it.


> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

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

One more question: Since TableInputFormat.configure does an open table, do you think it is necessary to also do an openTable in HClient.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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Vuk Ercegovac commented on HADOOP-1519:
---------------------------------------

I use openTable in getStartKeys in order to make sure that tableServers is populated.
I'd like not to depend on the caller for this to be the case (even though there currently is no
other example of a caller).

I included openTable in TableInputFormat simply to follow the convention of openning a table before use.
The subsequent invocation of openTable by getStartKeys should be cheap (hashtable lookup).

BTW, why is there a distinction between openTable and enableTable?


> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

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

enableTable is the opposite of disableTable. These operations bring a table on-line or take it off-line respectively. The only real purpose for these APIs is for administrative operations that must be done when a table is not on-line (like addColumn for example).

In general, I would not recommend calling enableTable as tables are on-line by default and if a table is off-line, it means that an administrator is performing an off-line operation on it.

With respect to openTable, all the other table oriented operations (startUpdate, obtainScanner, get, etc) require openTable to be called first, so in the interest of consistency, I think getStartKeys should behave the same.

> 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: Jim Kellerman
>         Attachments: hbaseMR.tgz, 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

    Attachment: patch.txt

Applies and runs tests cleanly in my environment. See if Hudson agrees.

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

        Fix Version/s: 0.14.0
    Affects Version/s: 0.14.0
               Status: Patch Available  (was: Open)

Works in my environment. Confirm with Hudson prior to committing.

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Hadoop QA commented on HADOOP-1519:
-----------------------------------

-1, could not apply patch.

The patch command could not apply the latest attachment http://issues.apache.org/jira/secure/attachment/12360855/patch.txt as a patch to trunk revision r551979.

Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/348/console

Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

    Status: Open  (was: Patch Available)

Forgot to do svn update before generating patch

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

    Attachment: patch.txt

New patch after svn update

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Jim Kellerman updated HADOOP-1519:
----------------------------------

    Status: Patch Available  (was: Open)

Works in my environment confirm with Hudson

> 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
>
>
> 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.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase

Nick Burch (Jira)
In reply to this post by Nick Burch (Jira)

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

Hadoop QA commented on HADOOP-1519:
-----------------------------------

-1, could not apply patch.

The patch command could not apply the latest attachment http://issues.apache.org/jira/secure/attachment/12360856/patch.txt as a patch to trunk revision r551979.

Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/349/console

Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.

> 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
>
>
> 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.

12