[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057782#comment-14057782
]
Enis Soztutar commented on HBASE-11484:
---------------------------------------
We do not have WAL-based flush-less snapshots but once (if) we have them,
restore WILL be required no matter what. That was the reason why I did not go
with something like the above. I think we should to restore, but make it
transparent to the user. The job cleans after the restore dir if I remember it
right.
> Provide a way in TableSnapshotInputFormat, not to restore the regions to a
> path for running MR every time, rather reuse a already restored path
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-11484
> URL: https://issues.apache.org/jira/browse/HBASE-11484
> Project: HBase
> Issue Type: New Feature
> Components: mapreduce
> Reporter: deepankar
> Priority: Minor
>
> We are trying to back a Hive Table by the Map Reduce over snapshots and we
> don't want to restore the snapshot to a restoreDir every time we want to
> execute a query. It would be nice if there is boolean in the function
> *TableSnapshotInputFormat.setInput* and exposed outside in the
> *TableMapReduceUtil.initTableSnapshotMapperJob*, with this boolean
> it will check whether the snapshot and the restore dir are in sync, rather
> than restoring again.
> Is this Idea looks Ok to you guys or you have any other suggestions, I will
> put up a patch for this if this idea is ok for guys
--
This message was sent by Atlassian JIRA
(v6.2#6252)
