[jira] [Commented] (AMBARI-24059) Ambari Views auto create instance should support matching to all known stacks

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

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

Hudson commented on AMBARI-24059:
---------------------------------

SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9436 (See [https://builds.apache.org/job/Ambari-trunk-Commit/9436/])
[AMBARI-24059] Ambari Views auto create instance should support matching (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=ab70364cf6432f71952f36d012e16cb2373f9a94])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/view/ViewRegistryTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java


> Ambari Views auto create instance should support matching to all known stacks
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-24059
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24059
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>   Original Estimate: 72h
>          Time Spent: 1.5h
>  Remaining Estimate: 70.5h
>
> The Ambari Views framework currently defines a set of configuration tags that can be used to configure the auto-instance deployment of a view.  Currently, this configuration allows for a matching stack to be explicitly configured, or a wildcard ('*") can be used to allow more flexible matching against a set of stack version numbers. 
> The current configuration already supports this type of matching: 
>  
> {code:java}
> <auto-instance>
> <name>AUTO_INSTANCE</name>
> <label>View Name</label>
> <stack-id>HDP-*</stack-id>
> :
> </auto-instance>{code}
> This configuration needs to be more flexible in order to allow a given View implementation to specify that it can match to any stack, including those defined outside of the "HDP" stack name. 
> The Ambari Views Registry should be updated to allow for specifying a wilcard character in order to instruct the Views framework to match against any stack, regardless of whether the stack begins with the "HDP" stack name. 
> {code:java}
> <auto-instance>
> <name>AUTO_INSTANCE</name>
> <label>View Name</label>
> <stack-id>*</stack-id>
> :
> </auto-instance>{code}
> This change should allow for greater flexibility for service and view developers, in cases where a given service's view can be used by more than one stack.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)