Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6DB95200CDB for ; Sat, 5 Aug 2017 21:12:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6A890164DCB; Sat, 5 Aug 2017 19:12:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ACDF0164DBC for ; Sat, 5 Aug 2017 21:12:21 +0200 (CEST) Received: (qmail 56995 invoked by uid 500); 5 Aug 2017 19:12:20 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 56984 invoked by uid 99); 5 Aug 2017 19:12:20 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Aug 2017 19:12:20 +0000 Received: from vrozov.local (c-71-204-190-196.hsd1.ca.comcast.net [71.204.190.196]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D50071A00A6 for ; Sat, 5 Aug 2017 19:12:19 +0000 (UTC) Subject: Re: Input needed for ApexCli. To: dev@apex.apache.org References: <967E9B49-2476-4B06-AA31-449DE4971EDA@datatorrent.com> From: Vlad Rozov Organization: Apache Apex Message-ID: Date: Sat, 5 Aug 2017 12:12:15 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US archived-at: Sat, 05 Aug 2017 19:12:22 -0000 I don't see need for the flag either. The output of the command should be what applications were stopped/shutdown and which one were not (for any reason). Thank you, Vlad On 8/4/17 23:21, Sanjay Pujare wrote: > +1 for best effort. I don't think a flag to offer alternative behavior is > of much value. > > On Aug 5, 2017 11:31 AM, "AJAY GUPTA" wrote: > >> It could be useful to have a flag and let user decide the best approach fit >> for him. We can have the default behaviour as best-effort with support for >> Validate and fail via flag. >> >> Ajay >> >> On Sat, 5 Aug 2017 at 8:33 AM, Bhupesh Chawda >> wrote: >> >>> +1 for best effort with warnings. >>> >>> ~ Bhupesh >>> >>> On Aug 4, 2017 23:46, "Pramod Immaneni" wrote: >>> >>>> I would prefer "Best effort" with warnings for the ones that are >> invalid. >>>> On Fri, Aug 4, 2017 at 9:42 AM, Florian Schmidt < >> florian@datatorrent.com >>>> wrote: >>>> >>>>> Hey everyone, >>>>> >>>>> I am currently extending the ApexCli so that the `shutdown-app` >> command >>>>> supports the both the appId and the appName as an argument (see >>>>> https://issues.apache.org/jira/browse/APEXCORE-767 < >>>>> https://issues.apache.org/jira/browse/APEXCORE-767>) >>>>> >>>>> During the review of the pull request, the following discussion came >>> up: >>>>> When a user passes multiple appNames / appIds to the shutdown command >>>>> (e.g. shutdown-app appA appB appC) and e.g. appB does not exists, >> which >>>> one >>>>> of the two approaches do we want to go: >>>>> >>>>> "Best effort”: Try to shutdown all those apps where we can find an >> app >>> to >>>>> the provided appName or appId. Print a warning if an app cannot >> found. >>>>> “Validate and Fail”: Validate that all apps can be found by the >>> provided >>>>> appId / appName. Do not run the command if one of the apps can’t be >>> found >>>>> This decision would probably influence the behavior of other CLI >>> commands >>>>> in the future as well, so that they all behave in a consistent way. >>> What >>>>> are your opinions? >>>>> >>>>> Regards >>>>> >>>>> Florian >>>>> >>>>> >>>>> >>>>>