-
Beta Was this translation helpful? Give feedback.
Answered by
jiayuasu
May 28, 2025
Replies: 2 comments
-
|
This means the sedona jars were not found. Are you sure they were loaded into |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
OK. You will need to run the following code (basically explicitly call I don’t know why the |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
jiayuasu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

OK. You will need to run the following code (basically explicitly call
SedonaContext.create).I don’t know why the
createis needed since Sedona on Databricks alreay did the same via the SesonaSqlExtension in config. But anyway, this fixes the issue