falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesan Ramachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1875) Import/Export : Replication coordinator gets created when export is used
Date Thu, 24 Mar 2016 21:51:25 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15211009#comment-15211009
] 

Venkatesan Ramachandran commented on FALCON-1875:
-------------------------------------------------

Hi [~pallavi.rao], This is expected behavior. If the feed has replication and export policies,
both export and replication coordinator will be created. 
It will be a legitimate use case if the feed in question is a derived dataset created on hadoop
(using pig/hive/mr/spark etc) and is pushed to an external relational database as well as
replicated to another hadoop cluster.

I'm closing this JIRA, but if you still see issues with this, please reopen.

Thanks


> Import/Export : Replication coordinator gets created when export is used
> ------------------------------------------------------------------------
>
>                 Key: FALCON-1875
>                 URL: https://issues.apache.org/jira/browse/FALCON-1875
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Pallavi Rao
>            Assignee: Venkatesan Ramachandran
>
> When I specify the export tag in the feed, even if I do not want replication, a replication
coordinator gets created. 
> This happens because we assume that existence of a target cluster means replication is
required. This is not true when I just want export.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message