You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Ajay Yadava (JIRA)" <ji...@apache.org> on 2016/01/25 18:39:40 UTC
[jira] [Comment Edited] (FALCON-1774) Falcon to honour PRISM_URL
env var
[ https://issues.apache.org/jira/browse/FALCON-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115610#comment-15115610 ]
Ajay Yadava edited comment on FALCON-1774 at 1/25/16 5:39 PM:
--------------------------------------------------------------
This is not error handling issue, this is by design, although in hindsight, not a good one.
was (Author: ajayyadava):
This is not error handling issue, this is by design.
> 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
(v6.3.4#6332)