Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 587F118CA5 for ; Tue, 17 Nov 2015 18:22:11 +0000 (UTC) Received: (qmail 44624 invoked by uid 500); 17 Nov 2015 18:22:11 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 44592 invoked by uid 500); 17 Nov 2015 18:22:11 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 44577 invoked by uid 99); 17 Nov 2015 18:22:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2015 18:22:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 073772C1F6A for ; Tue, 17 Nov 2015 18:22:11 +0000 (UTC) Date: Tue, 17 Nov 2015 18:22:11 +0000 (UTC) From: "Di Li (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-13903) Need a way to set "advanced" properties as optional (isRequired=false) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-13903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009176#comment-15009176 ] Di Li commented on AMBARI-13903: -------------------------------- [~natefalkibm] Hello Nathan, For example, if you look under Advanced core-site section, the Ambari web UI allows property "hadoop.security.key.provider.path" to be left blank (empty value). This is controlled on the core-site.xml level as shown below.... hadoop.security.key.provider.path true Have you tried specifying properties to allow empty values to meet your requirement? It's of course up to component's Python script to handle what it means for a prop to have an empty value... Di > Need a way to set "advanced" properties as optional (isRequired=false) > ---------------------------------------------------------------------- > > Key: AMBARI-13903 > URL: https://issues.apache.org/jira/browse/AMBARI-13903 > Project: Ambari > Issue Type: Improvement > Components: ambari-web > Affects Versions: 2.1.0 > Reporter: Nathan Falk > > The only way to let a configuration property be optional seems to be to define it in site_properties.js. It should be possible to specify required=false for any property in any xml file in the stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)