You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/06/20 23:36:24 UTC
[jira] [Updated] (AMBARI-6231) Views: parameterization of view
parameters
[ https://issues.apache.org/jira/browse/AMBARI-6231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-6231:
------------------------------------
Attachment: AMBARI-5940.patch
> Views: parameterization of view parameters
> ------------------------------------------
>
> Key: AMBARI-6231
> URL: https://issues.apache.org/jira/browse/AMBARI-6231
> Project: Ambari
> Issue Type: Task
> Components: controller
> Affects Versions: 1.7.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.7.0
>
> Attachments: AMBARI-5940.patch
>
>
> In a lot of cases, folks will want to use viewContext.getUsername with their view instances parameters. Right now, we leave that logic + code to the view developer. We should support parametrization of view instance params to handle this, and provide username as the first supported param.
> For example, say I have a parameter "view.path" : "/tmp/some/path"
> In my view, I want to append username, so I have logic in my view code to get view.path and + viewContext.getUsername()
> viewContext.getProperties().get("view.path") + "/" + viewContext.getUsername()
> resulting in /tmp/some/path/horton
> If views support parametrization, i could do this:
> "view.path" : "/tmp/some/path/$
> {username}
> "
> then all I need to do viewContext.getProperties().get("view.path");
--
This message was sent by Atlassian JIRA
(v6.2#6252)