Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Date: Mon, 17 Jul 2017 08:08:00 +0000 (UTC)
From: "Denes Bodo (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12923442.1450708618000.260436.1500278880234@Atlassian.JIRA>
In-Reply-To: <JIRA.12923442.1450708618000@Atlassian.JIRA>
References: <JIRA.12923442.1450708618000@Atlassian.JIRA> <JIRA.12923442.1450708618698@jira-lw-us.apache.org>
Subject: [jira] [Updated] (FALCON-1685) CLI does not honour extra attributes
 passed via client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Jul 2017 08:18:57 -0000


     [ 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 code.
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, 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)