ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13280) Enhanced Configs ui work to add Ranger User Info tab
Date Thu, 01 Oct 2015 17:01:26 GMT

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

Hadoop QA commented on AMBARI-13280:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12764566/AMBARI-13280.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified
test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3887//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3887//console

This message is automatically generated.

> Enhanced Configs ui work to add Ranger User Info tab
> ----------------------------------------------------
>
>                 Key: AMBARI-13280
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13280
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server, ambari-web
>    Affects Versions: 2.1.3
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13280.patch
>
>
> Currently, there is a notion of tab, section and subsection in UI which is completely
theme driven from stack API endpoint.
> subsection is the last container that contains set of configs. This is achieved by registering
each config with a subsection in service theme.
> As part of this ticket add a notion of subsection-tabs (a group of tabs) which can be
optionally present inside a subsection. Any config can register only to a subsection as it
does currently or can register to a subsection and to an individual tab of a subsection-tab
located inside the subsection.
> For now, Layout of a subsection-tabs (a group of tabs) in a subsection is always at last.
This means that if there are configs that are not mapped to any individual tab of subsection-tabs
then they will be placed before subsection-tabs. Orientation of configs inside subsection-tabs
should be in order of their occurrence in theme.json.



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

Mime
View raw message