You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sushanth Sowmyan (JIRA)" <ji...@apache.org> on 2012/08/07 23:47:10 UTC
[jira] [Commented] (HIVE-3341) Making hive tests run against
different MR versions
[ https://issues.apache.org/jira/browse/HIVE-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430651#comment-13430651 ]
Sushanth Sowmyan commented on HIVE-3341:
----------------------------------------
Phabricator review request posted at : https://reviews.facebook.net/D4557
With the patch attached, I compile/build as follows:
{noformat}
ant clean && ant very-clean && ant package
{noformat}
To test against 20:
{noformat}
ant test -Dhadoop.mr.rev=20 -Dtest.print.classpath=true
{noformat}
To test against 20S:
{noformat}
ant test -Dhadoop.mr.rev=20S -Dtest.print.classpath=true
{noformat}
To test against 23:
{noformat}
ant test -Dhadoop.mr.rev=23 -Dtest.print.classpath=true -Dhadoop.version=2.0.0-alpha -Dhadoop.security.version=2.0.0-alpha
{noformat}
( Note that 23 currently fails due to the MiniMR issue raised in HIVE-3156.)
> Making hive tests run against different MR versions
> ---------------------------------------------------
>
> Key: HIVE-3341
> URL: https://issues.apache.org/jira/browse/HIVE-3341
> Project: Hive
> Issue Type: Bug
> Reporter: Sushanth Sowmyan
> Assignee: Sushanth Sowmyan
>
> After we build hive, we want to have the ability to run unit tests against specific hadoop versions. Currently, the classpath constructed has multiple hadoop jars, which makes compiling okay, but running non-deterministic.
> An example is HIVE-3156, where running against 0.23 shows issues with a couple of tests (which should either be shimmed out, or separated into directories the way it's done in the shims/ directory) - It would also be nice to find these issues out at test-compile time itself, rather than having them fail at test runtime.
--
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