[
https://issues.apache.org/jira/browse/ARROW-8342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076655#comment-17076655
]
Wes McKinney edited comment on ARROW-8342 at 4/6/20, 8:53 PM:
--------------------------------------------------------------
Are there any problems beyond the return value of the {{.metadata}} property?
It seems like the simplest thing is to convert {{KeyValueMetadata}} to dict
when returning from this property. We can revert, too, but IMHO it will create
more work in aggregate. Ultimately we need to be able to faithfully access the
data in a KeyValueMetadata
was (Author: wesmckinn):
Are there any problems beyond the return value of the {{.metadata}} property?
It seems like the simplest thing is to convert {{KeyValueMetadata}} to dict
when returning from this property
> [Python] dask and kartothek integration tests are failing
> ---------------------------------------------------------
>
> Key: ARROW-8342
> URL: https://issues.apache.org/jira/browse/ARROW-8342
> Project: Apache Arrow
> Issue Type: Bug
> Components: Python
> Reporter: Joris Van den Bossche
> Priority: Blocker
> Fix For: 0.17.0
>
>
> The integration tests for both dask and kartothek, and for both master and
> latest released version of them, started failing the last days.
> Dask latest:
> https://circleci.com/gh/ursa-labs/crossbow/10629?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
>
> Kartothek latest:
> https://circleci.com/gh/ursa-labs/crossbow/10604?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
> I think both are related to the KeyValueMetadata changes (ARROW-8079).
> The kartothek one is clearly related, as it gives: TypeError:
> 'pyarrow.lib.KeyValueMetadata' object does not support item assignment
> And I think the dask one is related to the "pandas" key now being present
> twice, and therefore it is using the "wrong" one.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
