- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 03:03 AM
Hi,
I'm experiencing issues installing a library in my Databricks cluster due to a Maven dependency resolution error. Specifically, when trying to install or use libraries that depend on net.minidev:json-smart, I get the following error:
- Manually specifying json-smart:2.4.8 in the cluster library settings.
- Adding alternative repositories (https://repo1.maven.org/maven2/, https://jitpack.io).
- Cleaning the cluster library cache and restarting.
- Excluding json-smart from Azure SDK dependencies to force a specific version.
None of these have resolved the issue. Has anyone encountered this problem in Databricks? Any suggestions on how to force a specific version or work around the Maven metadata issue?
Thanks in advance!
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 06:04 AM
To avoid this issue, I manually excluded the json-smart dependency when installing affected libraries and forced a stable version instead.
If you're facing this issue, this could be a viable solution until the json-smart team fixes the metadata in Maven Central.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 06:04 AM
Same problem, same tests, same results. Currently working on it, support is very appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 06:04 AM
To avoid this issue, I manually excluded the json-smart dependency when installing affected libraries and forced a stable version instead.
If you're facing this issue, this could be a viable solution until the json-smart team fixes the metadata in Maven Central.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 06:13 AM
Thanks VitorFerron, exlcuding json-smart dependency worked for installing affected library with Maven (azure-eventhubs-spark_2.12:2.3.22 in my case).
When you say force a stable version instead, do you mean explicitly install json-smart library on cluster with Maven (in my case net.minidev:json-smart:2.3 for example)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-12-2025 06:22 AM
You're welcome
Yes, by ‘stable version,’ I mean using a Spark connector version that allows excluding json-smart. Installing an older version manually (like 2.3) may still cause issues, so if excluding it works, I’d recommend sticking with that approach.

