mjohns-databricks commented on issue #2472: URL: https://github.com/apache/sedona/issues/2472#issuecomment-3497373626
@CommanderWahid You will want to run on classic compute vs Serverless. Also, configure with Access Mode of [Dedicated](https://docs.databricks.com/aws/en/compute/dedicated-overview) vs Standard for full JVM permissions. Note: classic compute uses spark classic (vs spark connect), meaning serialization / deserialization of UDTs shouldn't be an issue. > We removed that init script and instead add them both in the libraries tab on the cluster which seems to be the new way?! It is preferred to avoid init scripts, though they are still allowed on classic compute. > I'm not sure how the namespace clashes can be resolved between Databricks Spatial SQL functions and the ones Sedona creates (for example on ST_Point as you demonstrated) This is a challenge that will be best addressed by Sedona solving Issue #2397. Please weigh in there. -- 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]
