hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19494) Create simple WALKey filter that can be plugged in on the Replication Sink
Date Tue, 19 Dec 2017 21:53:01 GMT

     [ https://issues.apache.org/jira/browse/HBASE-19494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-19494:
    Release Note: 
Adds means of adding very basic filter on the sink side of replication. We already have a
means of installing filter source-side, which is better place to filter edits before they
are shipped over the network, but this facility is needed by hbase-indexer.

Set hbase.replication.sink.walentrysinkfilter with a no-param Constructor implementation.
See test in patch for example.

> 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-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

View raw message