[
https://issues.apache.org/jira/browse/TEZ-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072554#comment-14072554
]
Hitesh Shah commented on TEZ-1300:
----------------------------------
bq. Some more details please ?
{code}
+ * <li> To use a single .tar.gz or .tgz file (generated by the tez build),
the full path to this
+ * file (including filename) should be specified. The internal structure of
the uncompressed tgz
+ * will be retained under $CWD/tez.</li>
{code}
bq. Do you have a suggestion on fixing this ? We use HADOOP_CLASSPATH_FIRST,
which should work - even if there's two copies of jars. One possible option is
to specify the partial build as the one which needs to be setup on the client.
If possible, let us use only one. Having 2 different types will be very
confusing for users. Similar comment for partial tarballs - can we figure out a
way to steer users more towards the recommended option - maybe document the
second option in an addendum after the initial guide?
bq. This is something which needs to be figured out. Currently we have three
targets. 1) full - which depending on command line options generates either a
dir / tar.gz etc. 2) partial - which also depends on the same command line
option. 3) full-tarball which always generates a .tgz file.
Not sure why option 3 is needed. Shouldn't doing a -Dtar on option 1 be enough?
Are the structures of the 2 tarballs different?
> Change default tez classpath to not include hadoop jars from the cluster
> ------------------------------------------------------------------------
>
> Key: TEZ-1300
> URL: https://issues.apache.org/jira/browse/TEZ-1300
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: TEZ-1300.1.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
