hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vuk Ercegovac (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-1519) mapreduce input and output formats to go against hbase
Date Thu, 28 Jun 2007 20:30:04 GMT

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

View raw message