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


   # 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 #132
   
    # 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, it is assumed that all parquet files in a listing scan will have 
the same schema. This will allow support for schema evolution in the underlying 
storage layer by merging parquet schemas on read. 
   
   # 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.
   -->
   
   There are three parts:
   1. Modify `ParquetFormat` to merge schemas for all listed parquet files 
using the underlying `Schema::try_merge` method in `arrow-rs`
   2. When reading individual parquet files, map projected column indexes from 
the merged schema to the file schema. 
   3. "Backfill" any missing columns from the merged schema with null-valued 
columns.   
   
   # Are there any user-facing changes?
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   Scans that contain heterogenous schemas will attempt to merge the schemas. 
If that error was expected then the observed behavior will be different. 
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->
   
   No
   


-- 
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-unsubscr...@arrow.apache.org

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


Reply via email to