Yes, right now we're using "${PWD}/archivename"
Madhu
On Wednesday, October 5, 2016 10:28 AM, Hitesh Shah
wrote:
From the current dir perspective, the classpath could be set up to use
“$PWD/archivename/*” where PWD in the container’s env would point to the
container’s working direct
From the current dir perspective, the classpath could be set up to use
“$PWD/archivename/*” where PWD in the container’s env would point to the
container’s working directory. This is a bit more robust as compared to using
“./“. Both should ideally work in most scenarios but using “./“ is depende
Seems like with this approach, there is no need to have information on current
dir.
thanks,Madhu
On Tuesday, October 4, 2016 4:44 PM, Hitesh Shah wrote:
The env is one approach for augmenting classpath. The other approach which
modifies classpath for both the AM and the task containers
The env is one approach for augmenting classpath. The other approach which
modifies classpath for both the AM and the task containers is to use
“tez.cluster.additional.classpath.prefix” by setting it to something like
“./archive name/*”
— Hitesh
> On Oct 4, 2016, at 4:38 PM, Madhusudan Ramann
Actually, we solved it using
tez.task.launch.env in tez-site.xml
thanks,Madhu
On Tuesday, October 4, 2016 11:13 AM, Madhusudan Ramanna
wrote:
Please note that we need this in the tez containers
thanks,Madhu
On Tuesday, October 4, 2016 11:11 AM, Madhusudan Ramanna
wrote:
He
Please note that we need this in the tez containers
thanks,Madhu
On Tuesday, October 4, 2016 11:11 AM, Madhusudan Ramanna
wrote:
Hello Folks,
We have an archive local resource that is being expanded to
PWD//*.*
How do we add PWD/ to classpath and java.library.path ?
thanks,Madhu
