-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency conflict between guava versions of spark and google storage api #4414
Comments
@lanastazia did you try excluding the older version of Guava? |
@ajaaym yes, I tried to exclude the older version of Guava evicted by the latest one, but it doesn't work. |
@lanastazia please add spark.executor.userClassPathFirst=true and spark.driver.userClassPathFirst=true in properties as below. |
It works, thanks a lot ! |
@elharo @saturnism FYI, another diamond dependency related to guava. |
@ajaaym, I don't think this very related to Guava. I think I root-caused this in grpc/grpc-java#5592 (comment) . I think that Guava is just what failed first. I believe Protobuf also would have failed. This is not the standard diamond dependency issue, either. It relates to class loaders, not package managers. |
Hello,
I’m deploying a Spark application, that has a dependency on the google storage java client, to list files in the bucket, and treat them one after another with Spark.
It seems that adding this dependency along with Spark causes a conflict with guava, and all my attempts to exclude certain guava (like here https://stackoverflow.com/questions/44935550/gae-cloud-storage-guava-nosuchmethoderror-on-appspot), try different guava versions and spark versions don’t succeed.
The error is only triggered in “assembly” mode (required to run the spark application on Dataproc), not when the application is run in local.
Do you know if there is a way to make these two libraries compatible?
Here is an example to reproduce this error https://github.com/lanastazia/spark-guava-issue
Here is the whole trace of this error :
Thanks !
The text was updated successfully, but these errors were encountered: