[
https://issues.apache.org/jira/browse/HIVE-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294644#comment-13294644
]
Carl Steinbach commented on HIVE-3131:
--------------------------------------
bq. Today there is no clean solution for this other than replacing the Hadoop
jar files from build\ivy (Default, Shims, test) folders.
A clean solution that leverages the current build infrastructure is to publish
the unreleased Hadoop jar files to the local Ivy/Maven repository. I think it
would be better to document this approach than to further complicate the build
scripts with the option of circumventing Ivy to resolve Hadoop dependencies.
> Allow to run Hive unit tests against unreleased versions of Hadoop
> ------------------------------------------------------------------
>
> Key: HIVE-3131
> URL: https://issues.apache.org/jira/browse/HIVE-3131
> Project: Hive
> Issue Type: Improvement
> Components: Testing Infrastructure
> Reporter: Kanna Karanam
>
> Sometimes It is required to run hive unit tests against unreleased versions
> of Hadoop during development stage. Today there is no clean solution for this
> other than replacing the Hadoop jar files from build\ivy (Default, Shims,
> test) folders. It will be more convenient for the developers if they can set
> the Hadoop version, and the location of Hadoop jar files as part of the “ant
> test”
> Ant clean test –DhadoopVersion=”x.y.z” –DhaoodLocalPath=”folder location to
> hadoop jars”
--
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
