paleolimbot commented on issue #3153: URL: https://github.com/apache/sedona/issues/3153#issuecomment-5133870357
I don't see this as an alignment issue...Sedona users migrating to SedonaDB may see an error and can make their CRS explicit with `ST_SetCrs()` or `ST_SetSRID()`. They should be doing this anyway, particular for raster inputs. The resulting code will run on both engines. We could also adopt type-level CRS tracking for Rasters, too (which would allow this error to be caught at planning time). The issue with the silent assumption s that can produce silently incorrect results rather than an error. As a migration path for Sedona Spark, you could have an opt in warning, followed by an opt out warning on the first instance of the encountered behaviour, followed by a behaviour change. If you don't get any feedback by the second stage, we will know this was behaviour that wasn't used anyway (do we have evidence that it's being used today?) -- 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]
