falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Praveen Adlakha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1774) Falcon to honour PRISM_URL env var
Date Tue, 26 Jan 2016 09:30:39 GMT

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

Praveen Adlakha commented on FALCON-1774:

Its not coming now.I checked in distributed mode.
dataqa@blr-test-129:/usr/local/falcon/falcon-distributed-0.10-SNAPSHOT$ bin/falcon entity
-type process -name DWH-CI-daily-supply5 -delete
falcon/DWH-CI-daily-supply5(process) doesn't exist. Nothing to do
prism/DWH-CI-daily-supply5(process) doesn't exist. Nothing to do 

> 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