You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "sandeep samudrala (JIRA)" <ji...@apache.org> on 2017/07/18 04:56:00 UTC
[jira] [Commented] (FALCON-1685) CLI does not honour extra
attributes passed via client
[ https://issues.apache.org/jira/browse/FALCON-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091105#comment-16091105 ]
sandeep samudrala commented on FALCON-1685:
-------------------------------------------
[~dionusos] : Falcon has moved to pull request model rather than patch mode. Can you raise your patch as pull request and can be reviewed there?
Thanks.
> CLI does not honour extra attributes passed via client
> ------------------------------------------------------
>
> Key: FALCON-1685
> URL: https://issues.apache.org/jira/browse/FALCON-1685
> Project: Falcon
> Issue Type: Bug
> Components: client
> Reporter: Pragya Mittal
> Assignee: Denes Bodo
> Attachments: 0001-FALCON-1685-CLI-does-not-honour-extra-attributes-pas.patch, 0001-FALCON-1685-CLI-does-not-honour-extra-attributes-pas.patch
>
>
> Falcon client takes in extra parameters passed to it by user and shows results, although these properties are filtered before passing to api.
> Instead CLI should throw error in such cases.
> One use case is :
> list operation does not use native scheduler property, but if I give the following command it gives expected result :
> {noformat}
> falcon entity -type process -list -properties falcon.scheduler:native
> 1
> (PROCESS) native-1
> {noformat}
> In such cases user assume that scheduler is able to handle list operation too.
> The same behaviour was shown by other falcon CLI operations.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)