[
https://issues.apache.org/jira/browse/TEZ-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952010#comment-16952010
]
Zoltan Haindrich commented on TEZ-4089:
---------------------------------------
yeah! ...and it mentions the minimal tarball ....but its unfortunate what
happens with it:
{quote}
Create a top-level directory called apache-tez-{x.y.z}-bin
Untar the contents of the minimal tarball into this directory.
Copy the full tarball into the directory under apache-tez-{x.y.z}-bin/share/
and name the file tez.tar.gz
Copy the LICENSE* files and NOTICE file from the full tarball and replace the
files under apache-tez-{x.y.z}-bin/ which came from the minimal tarball.
If the version is higher than 0.8.x, use the mvn javadoc command to generate
the xml-based config documentation and copy the files under
apache-tez-{x.y.z}-bin/conf/ with a .template suffix.
Tar the top-level directory and do the necessary signing as well as the
checksum creation as done for the src tarball.
{quote}
* because of the "directory creation" it no longer usable as a minimal tar.gz
* because its unpacked into a directory and not at / I can't copy it over (but
I tried it)
* I can copy the "full" tar.gz named "tez.tar.gz" - which is the only logical
move reading the installation docs...(at least for me) - but that is B type
installation
I think that Type A installation is not possible by using the released
artifacts.
> Upgrade to hadoop 2.8.4 to make 0.9.x releases work with Hive 3.x
> -----------------------------------------------------------------
>
> Key: TEZ-4089
> URL: https://issues.apache.org/jira/browse/TEZ-4089
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Priority: Major
> Attachments: TEZ-4089.branch-0.9.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> HADOOP-12209 have changed slightly the api of the FileStatus class - and
> because of that applications compiled against hadoop >=2.8 can't run with tez
> 0.9.x because of some exceptions arising from that.
> Right now I think its not possible to deploy an upstream hive release (which
> would use tez) without rebuilding tez along the way.
> http://mail-archives.apache.org/mod_mbox/tez-dev/201910.mbox/%3C0879b9ec-f334-2349-ca71-90ad053b20cd%40rxd.hu%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
