[
https://issues.apache.org/jira/browse/FALCON-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320185#comment-15320185
]
ASF GitHub Bot commented on FALCON-2014:
----------------------------------------
GitHub user pallavi-rao opened a pull request:
https://github.com/apache/falcon/pull/176
FALCON-2014 Issue with submit idempotency in distributed mode.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pallavi-rao/falcon 2014
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/falcon/pull/176.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #176
----
commit 98390d7372bd0bf0ec99a5dc375904f5735610be
Author: Pallavi Rao <[email protected]>
Date: 2016-06-08T07:23:53Z
FALCON-2014 Issue with submit idempotency in distributed mode
commit 21cdf697a4c1f2f434a4f32302d8b910e06f5516
Author: Pallavi Rao <[email protected]>
Date: 2016-06-08T07:33:21Z
FALCON-2014 Issue with submit idempotency in distributed mode. Message
update.
----
> Issue with submit idempotency in distributed mode
> -------------------------------------------------
>
> Key: FALCON-2014
> URL: https://issues.apache.org/jira/browse/FALCON-2014
> Project: Falcon
> Issue Type: Bug
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
>
> Lets say, a user submits an entity, entity1, against cluster1 and cluster2.
> Later, he submits the same entity, but with a different definition, against
> cluster3. Prism routes the request to cluster3 Falcon server. Since that
> server does not have entity1, it updates its config store (with a new
> definition).
> However, prism later fails the submit after a definition check (as it does
> not match with prev definition). Now, prism, cluster1 and cluster2 have
> definition1 and cluster3 has definition2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
