Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 15 Jul 2016 20:40:20 +0000 (UTC)
From: "Alejandro Fernandez (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12988061.1468091684000.45855.1468615220569@Atlassian.JIRA>
In-Reply-To: <JIRA.12988061.1468091684000@Atlassian.JIRA>
References: <JIRA.12988061.1468091684000@Atlassian.JIRA> <JIRA.12988061.1468091684757@arcas>
Subject: [jira] [Commented] (AMBARI-17641) Add storm impersonation
 authorized along with default ACL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 15 Jul 2016 20:40:22 -0000


    [ https://issues.apache.org/jira/browse/AMBARI-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380076#comment-15380076 ] 

Alejandro Fernandez commented on AMBARI-17641:
----------------------------------------------

I agree with [~sriharsha] that we don't have clear guidelines on which approach to use. Using variable names in configs is dangerous because they get saved in the database that way, so if the python variable name changes then we have to do a lot more work to fix it.
That being said, Sriharsha, can you submit a follow-on patch to use stack advisor instead. We can create another Jira to fix any existing configs that use this concept and then remove the code that does the variable interpretation.

> Add storm impersonation authorized along with default ACL
> ---------------------------------------------------------
>
>                 Key: AMBARI-17641
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17641
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Sriharsha Chintalapani
>            Assignee: Sriharsha Chintalapani
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17641.patch
>
>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)