[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated HBASE-12091:
----------------------------------
Attachment: 12091-v7-branch-1.txt
OK...
-v7:
* streamline the tests
* make sure all tests clean up after themselves
* adds a test for the case where the source table is not deleted
* allow a replication endpoint to determine the local configuration (via the
replication context)
* the sink will explicitly throw a table not found exception if one is
encountered. The details are not important for the source.
This works. Passes all tests. And the tests cover all scenarios that I can
think of.
This is more tricky than I thought. Please review carefully. Probably better to
wait until 1.4.1 still.
(Going to bed now)
> Optionally ignore edits for dropped tables for replication.
> -----------------------------------------------------------
>
> Key: HBASE-12091
> URL: https://issues.apache.org/jira/browse/HBASE-12091
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 1.4.0
>
> Attachments: 12091-branch-2.patch, 12091-v2-branch-1.txt,
> 12091-v3-branch-1.txt, 12091-v4-branch-1.txt, 12091-v5-branch-1.txt,
> 12091-v6-branch-1.txt, 12091-v7-branch-1.txt, 12091.txt
>
>
> We just ran into a scenario where we dropped a table from both the source and
> the sink, but the source still has outstanding edits that now it could not
> get rid of. Now all replication is backed up behind these unreplicatable
> edits.
> We should have an option to ignore edits for tables dropped at the source.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
