[query] Add to_pandas(types={}) argument to specify user-supplied pandas dtypes #12735
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
col1
andcol2
toint32
andnp.float64
, respectively, and allhl.tstring
fields 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...