[SPARK-55361][DOCS][PYTHON] suggest the use of to_arrow_schema to avoid specifying schema twice#54180
Open
casgie wants to merge 1 commit intoapache:masterfrom
Open
[SPARK-55361][DOCS][PYTHON] suggest the use of to_arrow_schema to avoid specifying schema twice#54180casgie wants to merge 1 commit intoapache:masterfrom
casgie wants to merge 1 commit intoapache:masterfrom
Conversation
…id specifying schema twice
JIRA Issue Information=== Documentation SPARK-55361 === This comment was automatically generated by GitHub Actions |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
suggest the use of to_arrow_schema to avoid specifying schema twice
What changes were proposed in this pull request?
python/docs/source/tutorial/sql/python_data_source.rstgives an example for using PyArrow RecordBatch.In the example, the Schema is specified twice, once for Spark
and then again for PyArrow
I am proposing to change the documentation to only specify a Spark schema and to use
pyspark.sql.pandas.types.to_arrow_schema()to convert the Spark schema to arrow.Why are the changes needed?
Using Python Data Source in production, having to specify the schema twice is a hassle and also a source for errors.
Does this PR introduce any user-facing change?
Yes, changes documentation.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
No