[
https://issues.apache.org/jira/browse/HIVE-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422856#comment-13422856
]
Carl Steinbach commented on HIVE-3303:
--------------------------------------
We should use the [INCLUDE|EXCLUDE]_HADOOP_MAJOR_VERSIONS macros to fix this.
The 0.23 behavior should be the standard going forward, so please create
mapreduce_stack_trace_h20.q and use the INCLUDE macro, and EXCLUDE 0.20 from
mapreduce_stack_trace.q
> Fix error code inconsistency bug in mapreduce_stack_trace.q and
> mapreduce_stack_trace_turnoff.q when running hive on hadoop23
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-3303
> URL: https://issues.apache.org/jira/browse/HIVE-3303
> Project: Hive
> Issue Type: Bug
> Reporter: Zhenxiao Luo
> Assignee: Zhenxiao Luo
>
> when running hive on hadoop23, mapreduce_stack_trace.q and
> mapreduce_stack_trace_turnoff.q are having inconsistent error code diffs:
> [junit] diff -a
> /home/cloudera/Code/hive/build/ql/test/logs/clientnegative/mapreduce_stack_trace.q.out
>
> /home/cloudera/Code/hive/ql/src/test/results/clientnegative/mapreduce_stack_trace.q.out
> [junit] < FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> [junit] > FAILED: Execution Error, return code 20000 from
> org.apache.hadoop.hive.ql.exec.MapRedTask. Unable to initialize custom script.
> [junit] diff -a
> /home/cloudera/Code/hive/build/ql/test/logs/clientnegative/mapreduce_stack_trace_turnoff.q.out
>
> /home/cloudera/Code/hive/ql/src/test/results/clientnegative/mapreduce_stack_trace_turnoff.q.out
> [junit] 5c5
> [junit] < FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.MapRedTask
> [junit] —
> [junit] > FAILED: Execution Error, return code 20000 from
> org.apache.hadoop.hive.ql.exec.MapRedTask. Unable to initialize custom script
> The error code 20000(which indicates unable to initialize custom script)
> could not be retrieved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
