yahoNanJing opened a new pull request #2065:
URL: https://github.com/apache/arrow-datafusion/pull/2065


   # Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   Closes #1772.
   
    # Rationale for this change
   <!--
    Why are you proposing this change? If this is already explained clearly in 
the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand your 
changes and offer better suggestions for fixes.  
   -->
   By splitting the object store into a separate module, the object stores in 
datafusion-contrib no longer need to depend on the whole datafusion crate. They 
only need to depend on this separated module. What's more, if we hope to 
introduce the object stores in datafusion-contrib as some featuers in the 
datafusion crate, the issue of dependency cyclic can be avoided.
   
   # What changes are included in this PR?
   <!--
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   - Introduces a new crate datafusion-storage for object store interfaces.
   - Moves the object store in previous datasource mod into this new 
datafusion-storage crate.
   
   # Are there any user-facing changes?
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->
   


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