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

Di Li commented on AMBARI-20737:
--------------------------------

the unit test that failed is unrelated to the changes introduced in this jira. 
it''s hive-env.xml with bad syntax.

validatePropertySchemaOfServiceXMLs(org.apache.ambari.server.state.ServicePropertiesTest)
  Time elapsed: 0.853 sec  <<< ERROR!
org.apache.ambari.server.AmbariException: File 
/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/ambari/ambari-server/target/test-classes/TestAmbaryServer.samples/../../../src/main/resources/common-services/HIVE/2.1.0.3.0/configuration/hive-env.xml
 didn't pass the validation. Error message is : The element type "deleted" must 
be terminated by the matching end-tag "</deleted>".
        at 
org.apache.ambari.server.state.ServicePropertiesTest.validatePropertySchemaOfServiceXMLs(ServicePropertiesTest.java:49)


> Able to hide the Use Public Repository option on Register Version page on 
> Ambari Admin View
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20737
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20737
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-admin, ambari-server
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: trunk
>
>         Attachments: AMBARI-20737.patch
>
>
> The Register Version UI page on Ambari Admin View shows two options related 
> to adding repo URLs: Use Public Repository and Use Local Repository.
> The Use Public Repository is disabled when no  stack repos are marked as 
> "stack_default=false" ( meaning it;s from the stack/repo URL defined in the 
> "latest" section in the repoinfo.xml)
> When repoinfo.xml does not have the latest section, however, the Use Public 
> Repository should be hidden from the view as it'd be definitely no 
> non-default stacks, and the "Why is this disabled ?" explanation does not 
> make sense in this case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to