[
https://issues.apache.org/jira/browse/HIVE-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751170#action_12751170
]
Todd Lipcon commented on HIVE-726:
----------------------------------
Yea, I think this is a nice-to-have but not complete blocker. Its value is that
you can ensure that you are still compatible with future releases. Since we
didn't shim the entirety of Hadoop, it's possible to compile against the
default fine, but still break at runtime if you're relying on an API that
doesn't exist in other versions. Occasionally compiling against all of the
"supported" versions is a good sanity check - if possible we should probably
set up Hudson tests that check against all of the supported Hadoop versions on
a nightly basis.
> Make "ant package -Dhadoop.version=0.17.0" work
> -----------------------------------------------
>
> Key: HIVE-726
> URL: https://issues.apache.org/jira/browse/HIVE-726
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Build Infrastructure
> Reporter: Zheng Shao
> Attachments: HIVE-726.1.patch, HIVE-726.2.patch, HIVE-726.3.patch,
> hive-726.txt
>
>
> After HIVE-487, users will have to specify the versions as in "shims/ivy.xml"
> to make "ant package -Dhadoop.version=<version>".work.
> Currently it is only running fine with the following versions (from
> shims/ivy.xml): 0.17.2.1, 0.18.3, 0.19.0, 0.20.0.
> We used to do "ant package -Dhadoop.version=0.17.0" but it's not working any
> more, although we can specify "ant package -Dhadoop.version=0.17.2.1" and the
> package will probably still work with 0.17.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
