tustvold opened a new pull request, #2220:
URL: https://github.com/apache/arrow-rs/pull/2220

   # 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.
   -->
   
   Part of #1764
   
   # 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.
   -->
   
   Whilst working on #1764 I realised we didn't have very good test coverage of 
writing arrow arrays with different encodings to parquet. This is because the 
arrow_reader fuzz tests write data using the `ColumnWriter` API and not the 
arrow writer API. 
   
   In the past these have boiled down to much the same thing, and so this 
hasn't been an issue. However, as we move to writing directly from arrow 
arrays, we introduce new codepaths that need testing
   
   # 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.
   -->
   
   Ensures good coverage of various encodings, writer versions, etc...
   
   # 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 `breaking 
change` label.
   -->
   
   No, this just changes some tests
   


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