CommanderWahid opened a new issue, #2397: URL: https://github.com/apache/sedona/issues/2397
Hi, I’m trying to use **Apache Sedona** in Databricks, alongside the new built-in Databricks spatial SQL functions. Right now, Sedona registers sql **ST** functions like st_distance, st_point ... This causes name collisions with some Databricks’ native spatial functions. It would be very useful if Sedona supported registering all SQL functions with a custom prefix, for example: st_distance -> sedona_st_distance st_point -> sedona_st_point This way, Sedona functions can coexist with Databricks functions in the same notebook without conflicts. Is this currently possible, or could it be added as a feature in a future release? Thank you! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
