[ 
https://issues.apache.org/jira/browse/TEZ-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951892#comment-16951892
 ] 

Zoltan Haindrich commented on TEZ-4089:
---------------------------------------

thank you [~jeagles], then I was looking into the right direction...but it 
still doesn't add up

lets stick with branch-0.9 for now...
* I've used hadoop 2.8.4 as 2.8.6 doesnt yet exists...

so I ended up with:  `mvn clean package -Phadoop28 -Dhadoop.version=2.8.4 
-DskipTests`
I have built the minimal and other tar.gz under tez-dist/target...

let's compare this to a "real" tez release:
```
wget https://www-eu.apache.org/dist/tez/0.9.2/apache-tez-0.9.2-bin.tar.gz
```

now there are many differences between these:
* the real release has some LICENSE/etc files and most importantly a "share" 
folder; under which there is a tez.tar.gz which seem to be the "full" tez tgz 
(with hadoop)
* the locally built "release" only contains a lib folder

I'm wondering about the following:
* how can we make sure that future releases do include the minimal tar.gz as 
well?
* where are the instructions by which the "released" thing gets built?
* running `git grep share` on tez sources pulls some results; but all of them 
are in license files...so I doubt that the source repo contains the logic which 
built the real "release"


> 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)

Reply via email to