paleolimbot commented on issue #1173: URL: https://github.com/apache/sedona-db/issues/1173#issuecomment-5305441214
It's a good question. I didn't think too hard when I was first writing the bindings and there isn't a ton of thought put in to the current default (a tibble with a GeoArrow shell column, that possibly should be ALTREP instead of the S3 madness that it is). I'm hesitant to materialize to sf by default because that materialization is slow and creates a lot of SEXPs, which can slow down the garbage collector considerably when we get millions of rows. Sometimes the next thing is Arrow anyway, where the current output would serve zero copy. We could add another function `sd_collect_sf()`, an option to `collect()`, or something else if that behaviour is useful! -- 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]
