falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-28) unable to submit/delete feed or process which had been attempted submit with wrong cluster
Date Fri, 21 Mar 2014 05:49:42 GMT

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

Shwetha G S commented on FALCON-28:

Don't you think the colo needs to be validated and fail early? Why should colo be a free form
string with no enforcement.
Yes, we should. Its tracked in https://issues.apache.org/jira/browse/FALCON-109

> 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

View raw message