teh-cmc commented on PR #6300: URL: https://github.com/apache/arrow-rs/pull/6300#issuecomment-2328361124
> I think this would be my preference, if only because it is much easier to understand the ramifications of such a change. Such a method should be relatively easy to add to the relevant ArrayBuilders, and therefore not hugely disruptive. I'm fine going down that route, but we would need for `shrink_to_fit` to be implemented on `Array` directly in our case, not `ArrayBuilders`. We keep a lot of Arrow data in long-lived memory storage, and therefore must be guaranteed that the data has been optimized for space before it gets committed to storage, regardless of how it got built or how it got there. Is that still okay? -- 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]
