[
https://issues.apache.org/jira/browse/FALCON-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121326#comment-15121326
]
Ajay Yadava commented on FALCON-1774:
-------------------------------------
Falcon supports url option, users can set environment variables and use them
instead of typing the complete url. No support is needed from falcon for doing
this. Sanjeev's point was not to make an environment variable available but to
pick it automatically if a forbidden command is put on the server instead of
the prism, which I have explained can be problematic in some scenarios.
> 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
> Attachments: FALCON-1774-v0.patch
>
>
> 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)
