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

   # 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 #.
   
   # Rationale for this change
   Introducing `Schema::field_names` method similar to Spark 
https://spark.apache.org/docs/1.6.1/api/java/org/apache/spark/sql/types/StructType.html#fieldNames()
   
   The method returns list of column names, including nested fields.
   
   Later we can use this code to improve schema output to be more user-friendly 
 
   or create toDDL() method, 
(https://spark.apache.org/docs/latest/api/java/org/apache/spark/sql/types/StructField.html#toDDL--)
 etc
   
   <!--
   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.
   -->
   
   # What changes are included in this PR?
   Bunch of extensions to query recursively fields and schema. Also changed an 
error message to have more details when schema and data mismatches
   
   <!--
   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.
   -->
   
   # Are there any user-facing changes?
   
   No
   <!--
   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.
   -->
   


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