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-9420) Configure Upgrade Task Needs to be More Flexible
Date Sun, 01 Feb 2015 23:01:34 GMT

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

Hadoop QA commented on AMBARI-9420:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12695836/AMBARI-9420.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 2 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-server:

                  org.apache.ambari.server.state.cluster.ClusterDeadlockTest

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

This message is automatically generated.

> Configure Upgrade Task Needs to be More Flexible
> ------------------------------------------------
>
>                 Key: AMBARI-9420
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9420
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9420.patch
>
>
> Consider the issue described in BUG-30470, where Hive's configure task has different
behavior based on an aspect of the system. As a result, the configure task should allow additional
elements/attributes that govern what to change and when.
> An example of this might be
> {code}
> <task xsi:type="configure">
>   <condition>
>       <property>hive.server2.transport.mode<property/>
>       <value>http</value>
>       <type>hive-site</type>
>       <key>hive.server2.http.port</key>
>       <value>10011</value>      
>   <condition>
>   <condition>
>       <property>hive.server2.transport.mode<property/>
>       <value>binary</value>
>       <type>hive-site</type>
>       <key>hive.server2.thrift.port</key>
>       <value>10010</value>      
>   <condition>
> </task>
> {code}
> Additionally, there can be more specific configure tasks as well. Such as a port configuration
task which knows to adjust the port by 10 beyond the current value.
> Existing configure tasks in the upgrade XML should be evaluated to determine what the
requirements are to allow for a more flexible upgrade script.



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

Mime
View raw message