[
https://issues.apache.org/jira/browse/HBASE-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422631#comment-13422631
]
stack commented on HBASE-6453:
------------------------------
So idea is you'd set this timestamp and we'd replicate from that time on?
What is the use case? Why not have replication happen when enabled?
You write the timestamp to zk under clusterid znode? Into a znode named
timefilter? The name should be timestamp? Or start_timestamp?
Thats great you added shell commands for setting/getting. Should they have
replication mentioned in command name so they are known to be replication
facility? Maybe its not necessary as long as these new commands are grouped w/
other replication commands (that is so?)
Thanks for the new feature Terry.
> Hbase Replication point in time feature
> ---------------------------------------
>
> Key: HBASE-6453
> URL: https://issues.apache.org/jira/browse/HBASE-6453
> Project: HBase
> Issue Type: New Feature
> Components: replication
> Affects Versions: 0.94.0
> Reporter: terry zhang
> Assignee: terry zhang
> Attachments: hbase-6453-v1.patch
>
>
> Now we can not control when hbase replication start to work. this patch
> support we set a time stamp filter . All the row which is below this time
> stamp will not be replicated. We also can delete and show this time stamp in
> hbase shell if we want to change it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
