You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Krisztian Szucs (JIRA)" <ji...@apache.org> on 2019/01/10 11:57:00 UTC

[jira] [Resolved] (ARROW-3918) [Python] ParquetWriter.write_table doesn't support coerce_timestamps or allow_truncated_timestamps

     [ https://issues.apache.org/jira/browse/ARROW-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krisztian Szucs resolved ARROW-3918.
------------------------------------
    Resolution: Duplicate
      Assignee: Krisztian Szucs

> [Python] ParquetWriter.write_table doesn't support coerce_timestamps or allow_truncated_timestamps
> --------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-3918
>                 URL: https://issues.apache.org/jira/browse/ARROW-3918
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>    Affects Versions: 0.11.1
>            Reporter: David Lee
>            Assignee: Krisztian Szucs
>            Priority: Major
>
> Error: Table Schema does not match schema used to create file.
> The 0.11.1 release added these parameters to pyarrow.parquet.write_table(), but they are missing from pyarrow.parquet.ParquetWriter.write_table().. I'm seeing mismatches between the table schema and the file schema, but they are identical in the error message with modified: timestamp[ms] column types in both schemas. The only thing which looks odd is the Pandas metadata that has a modified column with a panda datatype of datetime and a numpy datatype of datetime64[ns]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)