[
https://issues.apache.org/jira/browse/HBASE-19494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297260#comment-16297260
]
stack commented on HBASE-19494:
-------------------------------
See 001 [~whoschek] when you get a chance sir. It passes the Filter the
Connection in an init. I think this will work for you. Its ugly but less so
than having Connection implement a Replication Filter. Thanks.
> Create simple WALKey filter that can be plugged in on the Replication Sink
> --------------------------------------------------------------------------
>
> Key: HBASE-19494
> URL: https://issues.apache.org/jira/browse/HBASE-19494
> Project: HBase
> Issue Type: Sub-task
> Components: Replication
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0-beta-1
>
> Attachments:
> 0003-HBASE-19494-Create-simple-WALKey-filter-that-can-be-.patch,
> HBASE-19494.master.001.patch
>
>
> hbase-indexer used to look at WALKeys on the sink to see if their time of
> creation was before the time at which the replication stream was enabled.
> In the parent redo, there is no means for doing this anymore (because WALKey
> used to be Private and because to get at the WALKey in the Sink, you had to
> override all of the Replication which meant importing a million Private
> objects...).
> This issue is about adding a simple filter to Replication on the sink-side
> that just takes a WALKey (now InterfaceAudience LimitedPrivate and recently
> made read-only).
> Assigned myself. Need to do this so hbase-indexer can move to hbase2.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
