lys0716 commented on a change in pull request #23941: [MINOR][DOC] Add more 
details to descriptions of customized class path
URL: https://github.com/apache/spark/pull/23941#discussion_r261886382
 
 

 ##########
 File path: docs/configuration.md
 ##########
 @@ -441,7 +441,7 @@ Apart from these, the following properties are also 
available, and may be useful
   <td>false</td>
   <td>
     (Experimental) Same functionality as 
<code>spark.driver.userClassPathFirst</code>, but
-    applied to executor instances.
+    applied to executor instances. This is used in both cluster mode and 
client mode.
 
 Review comment:
   The reason is that the descriptions of 
<code>spark.driver.userClassPathFirst</code> said **This is used in cluster 
mode only**. But <code>spark.executor.userClassPathFirst</code> works for 
client mode as well.
   
   In our case, we use client mode. There is a use case that we want to 
overwrite executor class path. We try 
<code>spark.executor.extraClassPath</code>, but it is not enough. I had to use 
<code>spark.executor.userClassPathFirst</code> together.
   
   However, the descriptions of <code>spark.driver.userClassPathFirst</code> 
misleading us. We thought <code>spark.executor.extraClassPath</code> only works 
for cluster mode.
   
   The submission command would be something like 
   
   > ... --conf spark.executor.extraClassPath=JarA.jar \
   --conf spark.driver.extraClassPath=/path-to-jar/JarA.jar
   --conf spark.executor.userClassPathFirst=true
   ...
   --class package.JarAClass
   /path-to-jar/JarA.jar

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to