[
https://issues.apache.org/jira/browse/HBASE-12091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245249#comment-16245249
]
Lars Hofhansl edited comment on HBASE-12091 at 11/9/17 6:20 AM:
----------------------------------------------------------------
bq. Is there something that prevents this?
Not that I am aware of. I generally don't know how we send exceptions back to
the clients. Looks like it's going through Protobufs builtin ServiceException,
which is thrown internally.
Don't like the parsing either. At least now the sink controls exactly how the
exception is thrown, so it should be safe.
was (Author: lhofhansl):
bq. Is there something that prevents this?
Not that I am aware of. I generally don't know how we send exceptions back to
the clients. Will take a look.
Don't like the parsing either. At least now the sink controls exactly how the
exception is thrown, so it should be safe.
> 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: 2.0.0, 3.0.0, 1.4.1, 1.5.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-v7-master.txt,
> 12091-v8-master.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)
