You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Denes Bodo (JIRA)" <ji...@apache.org> on 2017/05/22 08:19:04 UTC

[jira] [Updated] (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:all-tabpanel ]

Denes Bodo updated FALCON-1685:
-------------------------------
    Attachment: 0001-FALCON-1685-CLI-does-not-honour-extra-attributes-pas.patch

Can you please review my suggestion? In case if the user wants an operation that does not support properties then an Exception will be thrown.

> 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
>         Attachments: 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.3.15#6346)