[AMBARI-9420] Configure Upgrade Task Needs to be More Flexible

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: ambari-server
• Epic Link: Ambari: Rolling Upgrade
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 01/Feb/15 21:43
• Updated: 02/Feb/15 22:54
• Resolved: 02/Feb/15 17:35

Description

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

<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>

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.

Issue Links

• links to: Reviewboard