You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Apache Arrow JIRA Bot (Jira)" <ji...@apache.org> on 2022/10/13 17:52:00 UTC

[jira] [Commented] (ARROW-11378) [C++][Dataset] Writing partitions with timestamp type give mis-formatted (integers) directory names

    [ https://issues.apache.org/jira/browse/ARROW-11378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617236#comment-17617236 ] 

Apache Arrow JIRA Bot commented on ARROW-11378:
-----------------------------------------------

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned per [project policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment]. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [C++][Dataset] Writing partitions with timestamp type give mis-formatted (integers) directory names
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-11378
>                 URL: https://issues.apache.org/jira/browse/ARROW-11378
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: C++
>            Reporter: Joris Van den Bossche
>            Assignee: Weston Pace
>            Priority: Major
>              Labels: dataset
>
> {code}
> In [1]: df = pd.DataFrame({"dates": list(pd.date_range("2012-01-01", periods=2, freq="D")) * 5, "col": range(10)})
> In [2]: table = pa.table(df)
> In [8]: part = ds.partitioning(table.select(["dates"]).schema, flavor="hive")
> In [9]: ds.write_dataset(table, "test_partition_timestamp", format="parquet", partitioning=part)
> In [10]: !ls test_partition_timestamp/
> 'dates=1325376000000000000'  'dates=1325462400000000000'
> {code}
> Same happens for non-ns timestamp types.
> (didn't directly find an existing issue about it)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)