You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2012/12/01 20:37:58 UTC
[jira] [Updated] (HIVE-3760)
TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
[ https://issues.apache.org/jira/browse/HIVE-3760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Chauhan updated HIVE-3760:
-----------------------------------
Attachment: hive-3760.patch
With this patch mapreduce_stack_trace.q doesn't run for hadoop-1 but mapreduce_stack_trace_hadoop20.q is run against hadoop-1. On hadoop-1 we are able to correctly capture mapreduce stack trace same as with hadoop20, so it make sense to run and check its output against mapreduce_stack_trace_hadoop20.q
With this patch this test passes on all of hadoop 0.20, 1.0 and 0.23.3
though actually mapreduce_stack_trace.q which after this patch will run only on 0.23.3 should fail because mapreduce_stack_trace.q.out contains incorrect results. In particular, it doesn't capture the stack trace which it should capture. Wil create a separate jira for it.
> TestNegativeMinimrCliDriver_mapreduce_stack_trace.q fails on hadoop-1
> ---------------------------------------------------------------------
>
> Key: HIVE-3760
> URL: https://issues.apache.org/jira/browse/HIVE-3760
> Project: Hive
> Issue Type: Bug
> Reporter: Ashutosh Chauhan
> Attachments: hive-3760.patch
>
>
> Actually functionality is working correctly, but incorrect include/exclude macro in test directive is making its .q.out comparison against incorrect results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira