ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <>
Subject [jira] [Updated] (AMBARI-11337) Ranger database check: Misc UI tweaks
Date Fri, 22 May 2015 12:50:17 GMT


Aleksandr Kovalenko updated AMBARI-11337:
    Attachment: AMBARI-11337.patch

> Ranger database check: Misc UI tweaks
> -------------------------------------
>                 Key: AMBARI-11337
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.1.0
>         Attachments: AMBARI-11337.patch
> Following issues needs to be resolved as part of this ticket:
> # On Select services page after selecting ranger and proceeding: Ambari web should not
have specific references to HDP or any other stack name. Remove reference to HDP 2.2. Instead
refer to Ranger 0.4.0 or show that specific requirement only if Ranger 0.4.0 is being installed
(again logic depending on Ranger service version rather than HDP version).
> # While landing on Customize services page JDBC driver warning is not shown until the
database option is changed. Expected behavior is to show the warning when user lands on the
page irrespective of the DB option value.
> # On switching to  Ranger service on customize services page, undo buttons are shown
by default for _Driver class name for a JDBC Ranger database_ and _Ranger DB host_ . Clicking
on undo button for _Driver class name for a JDBC Ranger database_ makes it blank. Expected
behavior is that no undo sign should be present for this property. It's behavior should be
similar to *JDBC connect string for a Ranger database*.  
> # Default value for *Ranger DB host* should be blank in stack meaning user should be
enforced to enter a value on customize service page.
> # User friendly name should be used for DB FLAVOR and it's options
> ** DB FLAVOR -> DB Flavor
> ** MYSQL -> Existing MySQL Database
> ** ORACLE -> Existing Oracle Database
> ** POSTGRES -> Existing PostgreSQL Database 
> ** MSSQL -> Existing Microsoft SQL Database
> # Show *SQL Command Invoker* on user interface only if it makes sense and user is likely
to tweak it. Otherwise depending upon the ranger JDBC driver class, SQL command invoker can
be derived on agent script and no need to expose it in ambari API and UI. 
> # The order of properties shown in DB settings section needs to corrected. In my opinion
"Ranger Server host, DB Flavor, Ranger DB host, Ranger DB username, Ranger DB password, Ranger
DB root user, Ranger DB root password, Ranger DB name, Driver class name for a JDBC Ranger
database, JDBC connect string for a Ranger database, *Test Connection*, Ranger Audit DB name,
Ranger Audit DB username, Ranger Audit DB password.

This message was sent by Atlassian JIRA

View raw message