[GH-1137] Document H3 version conflict workaround on Databricks#2632
Merged
[GH-1137] Document H3 version conflict workaround on Databricks#2632
Conversation
Databricks Runtime bundles H3 v3.x which conflicts with Sedona's H3 v4.x API, causing NoSuchMethodError when using ST_H3CellIDs and other H3 functions. - Add rm -f /databricks/jars/*h3*.jar to the init script to remove the conflicting JAR before copying Sedona's JARs - Add a 'Known issues' section explaining the H3 conflict and the fix - Rename 'Known bugs' to 'Known issues' for consistency
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Did you read the Contributor Guide?
Is this PR related to a ticket?
[GH-XXX] my subject. Closes H3 functions missing methods on Databricks:java.lang.NoSuchMethodError: com.uber.h3core.H3Core...#1137What changes were proposed in this PR?
Databricks Runtime bundles H3 v3.x, which conflicts with Sedona's H3 v4.x API. This causes
NoSuchMethodErrorwhen using Sedona's H3 functions (e.g.,ST_H3CellIDs) on Databricks.This PR updates the Databricks setup docs to:
rm -f /databricks/jars/*h3*.jarline (commented out) in the init script, with instructions to uncomment if H3 functions are needed