RogPodge commented on issue #196: [LIVY-606][LIVY-152] fix the invalid conf of 
pyspark.archives and sparkr.package
   >  Sorry, what do you mean "I can't seem to replicate the stated behavior on 
my machine after trying to incorporate this PR"?
   After porting your PR to my local Livy instance, I still see the following 
in the Livy logs when I try to submit a pyspark application. 
   INFO yarn.Client: Uploading resource file:/opt/spark/python/lib/ 
   I noticed that the PR only makes changes to the InteractiveSession.scala, so 
how do we ensure that the file is cached for Batch Sessions?

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to