[
https://issues.apache.org/jira/browse/AMBARI-9420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-9420:
------------------------------------
Attachment: AMBARI-9420.patch
> 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)
