[GitHub] [arrow-datafusion] yahoNanJing edited a comment on pull request #2076: Remove dependency of common for the storage crate

[GitBox <gi...@apache.org>]

yahoNanJing edited a comment on pull request #2076:
URL: https://github.com/apache/arrow-datafusion/pull/2076#issuecomment-1077732443


   > Can you just clarify how this will make it easier for datafusion core to depend on the object store extensions?
   
   Suppose we hope to introduce optional features of object store extensions in the datafusion core. Both of the datafusion core and the object store extensions should depend on the same storage crate, either by version or rev rather than by path. Then if the storage crate depends on the common crate, it will be not good for the common crate to have the same version or rev as the one for the storage crate. Otherwise, if the storage crate does not depend on any datafusion crate, it will be possible to make it stable with some version. And then both of the datafusion core and object store extensions depend on that version.
   
   > Piggy backing on @alamb's idea from yesterday, and in light of this change, im wondering if new crate for all listing related code could be `datafusion-storage-listing` to show how they are linked.
   
   I'm good with creating a new crate for the listing things. 
   


-- 
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: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org