You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/07/02 02:31:19 UTC

[GitHub] [spark] jerryshao commented on issue #24909: [SPARK-28106][SQL] When Spark SQL use "add jar" , before add to SparkContext, check jar path exist first.

jerryshao commented on issue #24909: [SPARK-28106][SQL] When Spark SQL use  "add jar" ,  before add to SparkContext, check  jar path exist first.
URL: https://github.com/apache/spark/pull/24909#issuecomment-507493512
 
 
   >Why I add a new API is to keep previous call stacks(core behavior,start progress etc.....) are unaffected. It only check user's add jar behavior and function registered like "CREATE FUNCTION FUNC USING /PATH/TO/JAR".
   
   I think we've never said that we should keep spark core unaffected, what we want is to get the right/expected behavior. So what we're discussing is to figure out a right solution for the fix, not a way to bypass the spark core.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org