[
https://issues.apache.org/jira/browse/HBASE-10642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13916685#comment-13916685
]
Nick Dimiduk commented on HBASE-10642:
--------------------------------------
My understanding from this ticket's description was that this would be a sample
implementation, and yet
{noformat}
+++
src/main/java/org/apache/hadoop/hbase/mapreduce/TableSnapshotInputFormat.java
(revision 0)
{noformat}
Wasn't the reason this feature didn't make it into 0.94 due to the lack of
interest for 0.96? This patch will result in a feature available in 0.94.18,
absent from the 0.96 line, and available again in 0.98. We've been bitten
enough by the mapreduce API shifting between releases underneath us, let's not
do the same to our users -- especially so close to 1.0. It's a valuable
capability, but I'm -1 on inconsistent APIs.
Speaking of inconsistent APIs, are there plans to provide an equivalent
implementation for the mapred API?
> Add M/R over snapshots sample code to 0.94
> ------------------------------------------
>
> Key: HBASE-10642
> URL: https://issues.apache.org/jira/browse/HBASE-10642
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 0.94.18
>
> Attachments: 10642-0.94-v2.txt, 10642-0.94.txt
>
>
> I think we want drive towards all (or most) M/R over HBase to be against
> snapshots and HDFS directly.
> Adopting a simple input format (even if just as a sample) as part of HBase
> will allow us to direct users this way.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
