You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Joris Van den Bossche (Jira)" <ji...@apache.org> on 2019/11/27 13:13:00 UTC
[jira] [Updated] (ARROW-7268) [Rust] Propagate `custom_metadata`
field from IPC message
[ https://issues.apache.org/jira/browse/ARROW-7268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joris Van den Bossche updated ARROW-7268:
-----------------------------------------
Summary: [Rust] Propagate `custom_metadata` field from IPC message (was: Propagate `custom_metadata` field from IPC message)
> [Rust] Propagate `custom_metadata` field from IPC message
> ---------------------------------------------------------
>
> Key: ARROW-7268
> URL: https://issues.apache.org/jira/browse/ARROW-7268
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Rust
> Reporter: Martin Grund
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Right now, the custom metadata field in the Schema IPC message is not propagated from the IPC message to the internal data type. To be closer to parity compared to the other implementations it would be good to add the necessary logic to serialize and deserialize.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)