[query] Add to_pandas(types={}) argument to specify user-supplied pandas dtypes#12735
Merged
danking merged 5 commits intohail-is:mainfrom Mar 5, 2023
Merged
[query] Add to_pandas(types={}) argument to specify user-supplied pandas dtypes#12735danking merged 5 commits intohail-is:mainfrom
danking merged 5 commits intohail-is:mainfrom
Conversation
Contributor
|
Amazing! I'll look into this this week. Thank you Masa! |
Contributor
|
@patrick-schultz I added some tests and fixed behavior as a result. I think this is a valuable change, but since I've edited it directly seems like someone else should do review as well. |
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
3 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.
This PR fixes #11738. Now users can specify arbitrary type conversation between Hail and Pandas dtypes via:
This maps
col1andcol2toint32andnp.float64, respectively, and allhl.tstringfields toobject.One design question might be whether to have separate arguments for column name and Hail type specifications or not. Any thoughts? cc: @danking
Also, I don't think the current type check would work for
np.float64-like numpy dtype specifications...