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


   # 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 #1060. It's a refactor version of PR #1062.
   
    # 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.  
   -->
   Currently, we can only read parquet files from local file system. It would 
be nice to add support to read parquet files that reside on HDFS.
   
   # 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.
   -->
   Introduced hdfs as one of the object store. With the feature of hdfs, it 
will depend on the fs-hdfs crate which provides the Rust client to hdfs. Then 
we can run some sql-based unit test with data on hdfs.
   
   # Are there any user-facing changes?
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   One example for querying on the hdfs data can be seen in the method of 
hdfs.run_with_register_alltypes_parquet in  tests/sql.rs. Firstly create a 
**HadoopFileSystem**. Then register it with **hdfs** scheme.
   
   <!--
   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