Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support FFI / C Data Interface for MapType #2037

Closed
wjones127 opened this issue Jul 10, 2022 · 0 comments · Fixed by #2042
Closed

Support FFI / C Data Interface for MapType #2037

wjones127 opened this issue Jul 10, 2022 · 0 comments · Fixed by #2042
Labels
arrow Changes to the arrow crate enhancement Any new improvement worthy of a entry in the changelog

Comments

@wjones127
Copy link
Member

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

MapType was added in #491, but is not yet supported in C Data interface. Users will currently experience this error:

other => Err(ArrowError::CDataInterface(format!(
"The datatype \"{:?}\" is still not supported in Rust implementation",
other
))),

Use use this FFI to move schemas from Rust-land to PyArrow-land in delta-rs.

Describe the solution you'd like

Add map type to current handling.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@wjones127 wjones127 added the enhancement Any new improvement worthy of a entry in the changelog label Jul 10, 2022
@alamb alamb added the arrow Changes to the arrow crate label Jul 21, 2022
@alamb alamb changed the title Support FFI / C Data Interface for MapType Support FFI / C Data Interface for MapType Jul 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arrow Changes to the arrow crate enhancement Any new improvement worthy of a entry in the changelog
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants