cetra3 commented on PR #10301: URL: https://github.com/apache/arrow-rs/pull/10301#issuecomment-5348694363
> I just started looking into the memory pool api, and am wondering which usecases would require the arrays to change owners. Maybe a second claim call with a different (non ptr-eq) MemoryPool should just not be allowed? This is driven by datafusion and attributing where the recordbatch lives within the execution tree. If you can't change the owner then you don't know what part of the tree is currently holding onto the memory. I.e, is it the `DataSourceExec` reading the parquet, or is it the `SortExec` that is bundling it up? -- 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]
