You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@sedona.apache.org by "mkaravel (via GitHub)" <gi...@apache.org> on 2025/11/06 22:50:48 UTC

Re: [I] [Databricks] Allow registering Sedona functions with a custom prefix [sedona]

mkaravel commented on issue #2397:
URL: https://github.com/apache/sedona/issues/2397#issuecomment-3499710032

   I think the problem is really at the SQL level. My understanding is that when Apache Sedona is installed on top of Databricks, the Apache Sedona ST expressions that are homonyms to the ones provided via Databricks override the Databricks ones in the function registry. Then when function resolution is happening in the SQL context the Apache Sedona get chosen over the Databricks ones which can cause failures in queries.


-- 
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-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org