teh-cmc commented on PR #6300: URL: https://github.com/apache/arrow-rs/pull/6300#issuecomment-2323010953
Uh-oh, I missed one! > Adding another API (if it doesn't already exist) to "shrink_to_fit" for Arrays in general That could be an alternative solution if this one doesn't cut it, yes. Beyond the fact that it is likely much more work, it does sound like an antipattern though: given that Arrow arrays are immutable once created, is there any situation in which you would ever want all that extra capacity to hang around? The only reason I can think of is if getting rid of that extra capacity comes at a performance cost, but as the benchmarks show above, this is not necessarily the case... -- 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]
