EmilyMatt opened a new issue, #544:
URL: https://github.com/apache/arrow-rs-object-store/issues/544

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   <!--
   A clear and concise description of what the problem is. Ex. I'm always 
frustrated when [...] 
   (This section helps Arrow developers understand the context and *why* for 
this feature, in addition to  the *what*)
   -->
   
   There is an issue with accounting for memory when fetching data using 
ObjectStore, I think since this project is works in tandem with arrow-rs and 
datafusion, there is value to using arrow-rs' Buffer types instead of the 
current raw bytes::Bytes implementation, Buffer provides similar functionality, 
including the zero-copy slicing and controlled ownership, but also not 
converting between containers let's us monitor the memory throughout the 
lifetime of the data.
   With the addition of the memory pool feature to arrow-rs itself, this 
becomes even more useful, as we could immediately register the memory in the 
object store, and have a very accurate account of the used memory throughout 
the application,
   this change is invaluable.
   
   **Describe the solution you'd like**
   <!--
   A clear and concise description of what you want to happen.
   -->
   
   Changing the entire API from using bytes::Bytes to using 
arrow_buffer::Buffer,
   this is a breaking change but I think it will have an important impact on 
the ecosystem.
   
   **Describe alternatives you've considered**
   <!--
   A clear and concise description of any alternative solutions or features 
you've considered.
   -->
   
   **Additional context**
   <!--
   Add any other context or screenshots about the feature request here.
   -->
   


-- 
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]

Reply via email to