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