paleolimbot commented on PR #1145: URL: https://github.com/apache/sedona-db/pull/1145#issuecomment-5254557834
One issue with this is: how do we ensure that the chunk index is not lying? SedonaDB internals typically see one raster a time, but an application using other columns can make sure that it's only working with a table that is a raster. From SedonaDB's end, we can't typically know if somebody has unioned this with some other raster table. (Feel free to correct me if I'm missing something here). Broadly this gets at the higher level question: is a raster a row, is a raster a column, or is a raster a table? Or do rasters participate in relational algebra at all? (i.e., should we always just keep Raster objects as Raster objects and write our own ExecutionPlans for these ops if we need to play games like this to get acceptable performance?) -- 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]
