[
https://issues.apache.org/jira/browse/FALCON-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shwetha G S updated FALCON-28:
------------------------------
Attachment: FALCON-28-v2.patch
Prism figures out which falcon servers to send the request to by looking at the
entity in config store. But at submit, the entity is still not in config store
and hence fails. Fixed this issue by getting colos from the entity in the
request
> unable to submit/delete feed or process which had been attempted submit with
> wrong cluster
> ------------------------------------------------------------------------------------------
>
> Key: FALCON-28
> URL: https://issues.apache.org/jira/browse/FALCON-28
> Project: Falcon
> Issue Type: Bug
> Components: prism
> Reporter: Samarth Gupta
> Assignee: Shwetha G S
> Fix For: 0.5
>
> Attachments: FALCON-28-v2.patch, FALCON-28.patch
>
>
> steps to reproduce:
> 1. submit a cluster with name "xyz" and colo "abc" . Make sure this colo is
> not mentioned in runtime properties of prism.
> 2. try to submit a feed with above cluster. It return a error while submit
> "Error:
> prism/org.apache.ivory.IvoryException::com.sun.jersey.api.client.ClientHandlerException:
> java.lang.IllegalArgumentException: URI is not absolute"
> 3. now correct the cluster in the feed to a one which is present in runtime
> properties and try submit again, we get following response "Error: (feed)
> <feed name> already registered with configuration store. Can't be submitted
> again. Try removing before submitting."
> 4. Now we are not able to delete the feed also and submit the correct feed as
> well.
> only 2 workaround possible currently , 1. change the name of feed or 2. clean
> the config store of prism
--
This message was sent by Atlassian JIRA
(v6.2#6252)
