falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denes Bodo (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1685) CLI does not honour extra attributes passed via client
Date Mon, 17 Jul 2017 08:08:00 GMT

     [ 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

Sorry for the late proposal I haven't had much time. Honestly I can understand why this ticket
is open for more than one and a half year.
I examined more alternatives and I think Falcon CLI commands are too complicated to use pleasant
Can you please comment on this change? If it is OK than I will continue implementing it. Positive
and negative comments are also welcome.

> 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,
> 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

View raw message