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

Hudson commented on AMBARI-20597:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20597 - Pig exectype default value seems to be not changing after 
(aonishuk: 
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=82e31c129c0645140443a4b693a9b182daed378e])
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
* (edit) 
ambari-server/src/main/resources/stacks/HDP/2.5/upgrades/config-upgrade.xml


> Pig exectype default value seems to be not changing after upgrade
> -----------------------------------------------------------------
>
>                 Key: AMBARI-20597
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20597
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: trunk
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.1
>
>         Attachments: AMBARI-20597.patch
>
>
> PIG in HDP 2.6 changes the default engine in {{pig-properties/content}} from 
> MapR to Tez:
> {code}
> exectype=tez
> {code}
> However, HDP upgrades are not working correctly because of a problem with the 
> upgrade configuration pack:
> {code}
> <definition xsi:type="configure" id="hdp_2_6_0_0_pig_use_tez">
>   <type>pig-properties</type>
>   <replace key="exectype" find="exectype=mapreduce" 
> replace-with="exectype=tez" />
> </definition>
> {code}
> There is no key named {{exectype}} in {{pig-properties}} ... there is only 
> {{pig-properties/content}}. This key needs to be changed to find/replace



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

Reply via email to