[
https://issues.apache.org/jira/browse/HBASE-11484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14057809#comment-14057809
]
deepankar commented on HBASE-11484:
-----------------------------------
Also in the case of WAL-based flush-less snapshots case also, will it be any
good? if we can provide this as an option whether to restore or not restore, If
it is be restored WAL be replayed and restored and HRegion objects are created
from the restoredDir. Other wise we can use the [~mbertozzi]'s suggested
approach to create the HRegion objects by adding all the relevant HFiles
without replaying any WAL edits (essentially if they are ok with loosing the
edits in memstore)
> 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)
