falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1774) Falcon to honour PRISM_URL env var
Date Mon, 25 Jan 2016 17:42:39 GMT

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

Ajay Yadava commented on FALCON-1774:

My only concern in automatically using PRISM_URL is when someone tries to delete it on a server
thinking it will delete only from that server. 

> Falcon to honour PRISM_URL env var
> ----------------------------------
>                 Key: FALCON-1774
>                 URL: https://issues.apache.org/jira/browse/FALCON-1774
>             Project: Falcon
>          Issue Type: Improvement
>            Reporter: Sanjeev T
>            Assignee: Praveen Adlakha
> When we submit/delete/update process or feed, and we have falcon server url in client.properties,
we cannot do the operation, and the output, doesn't make sense
> {noformat}
> $ falcon entity -type process -name  bad-process -delete
> ERROR: Not Found;
> {noformat}
> In such cases we need to pass -url $PRISM_URL, where PRISM_URL points to prism host service.
> Requirement:
> * error message should say what is not found or expected PRISM_URL
> * Allow to set env var PRISM_URL
> * When we do submit/delete/update it should use the env variable
> * In case of schedule/suspend it should honour as specified in the client.properties

This message was sent by Atlassian JIRA

View raw message