[jira] [Commented] (AMBARI-15821) Ability to provide logical urls to view instances

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-15821:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12798200/AMBARI-15821.trunk.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:red}-1 core tests{color}.  The patch failed these unit tests in ambari-admin ambari-server ambari-views ambari-web:

                  org.apache.ambari.server.controller.AmbariManagementControllerTest

                                      The test build failed in ambari-web 

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

This message is automatically generated.

> Ability to provide logical urls to view instances
> -------------------------------------------------
>
>                 Key: AMBARI-15821
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15821
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.0.0
>            Reporter: Ashwin Rajeev
>            Assignee: Ashwin Rajeev
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15821.2.trunk.patch, AMBARI-15821.trunk.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Support logical URL endpoints instead of being tied down to a version-and-build-number specific URL. This leads to user bookmarks breaking
> 1) For a given view, the Ambari Admin can create one (or more) vanity URLs.
> 2) This should be an optional configuration.
> 3) It would be main/views/VIEW_NAME/some-vanity-name, where some-vanity-name is what the user can enter.
> 4) The Admin can designate which specific instance of the view (regardless of version) a given vanity URL is associated with
> 5) End User can use that vanity URL and bookmark.



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