docs: add type mapping tables between PyIceberg and PyArrow#3098
Open
iamluan wants to merge 3 commits intoapache:mainfrom
Open
docs: add type mapping tables between PyIceberg and PyArrow#3098iamluan wants to merge 3 commits intoapache:mainfrom
iamluan wants to merge 3 commits intoapache:mainfrom
Conversation
Contributor
|
this is great, thank you! Perhaps we can add it to the API section https://py.iceberg.apache.org/api/ |
iamluan
force-pushed
the
docs-2226-typemapping-pyiceberg-pyarrow
branch
from
9e80178 to
26b12e0
Compare
Author
|
Thank you for your review. I have added the markdown to the API section. |
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
2 participants
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.
Closes #2226
Rationale for this change
This PR adds documentation with tables describing the type mapping between PyArrow and PyIceberg data types.
Are these changes tested?
Yes.
The changes are tested locally as shown in the image below.
Are there any user-facing changes?
Yes.
This PR adds new user-facing documentation.