remibaar commented on issue #1137: URL: https://github.com/apache/sedona/issues/1137#issuecomment-1836834288
I managed to solve the issue! Indeed it was related to the version of H3 that was being installed in the Databricks runtime. By adjusting the init script, I remove the older H3 jar from the Databricks jars. This solves the issue. This is the code for my new init script: ```bash %sh # Create init script cat > /dbfs/FileStore/sedona/scripts/sedona-init.sh <<'EOF' #!/bin/bash # # File: sedona-init.sh # # On cluster startup, this script will copy the Sedona jars to the cluster's default jar directory. # In order to activate Sedona functions, remember to add to your spark configuration the Sedona extensions: "spark.sql.extensions org.apache.sedona.viz.sql.SedonaVizExtensions,org.apache.sedona.sql.SedonaSqlExtensions" # Remove default H3 version of databricks, as it is compatible with Sedona > 1.5.0 rm -f /databricks/jars/*com.uber*h3*.jar # Copy jars cp /dbfs/FileStore/sedona/jars/*.jar /databricks/jars EOF ``` I will keep this issue open, because I am going to create a PR for a change in the docs. https://github.com/apache/sedona/blob/master/docs/setup/databricks.md -- 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. To unsubscribe, e-mail: issues-unsubscr...@sedona.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
