You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@parquet.apache.org by "Gabor Szadovszky (JIRA)" <ji...@apache.org> on 2018/04/18 12:23:01 UTC

[jira] [Closed] (PARQUET-1064) Deprecate type-defined sort ordering for INTERVAL type

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

Gabor Szadovszky closed PARQUET-1064.
-------------------------------------

> Deprecate type-defined sort ordering for INTERVAL type
> ------------------------------------------------------
>
>                 Key: PARQUET-1064
>                 URL: https://issues.apache.org/jira/browse/PARQUET-1064
>             Project: Parquet
>          Issue Type: Bug
>            Reporter: Zoltan Ivanfi
>            Assignee: Zoltan Ivanfi
>            Priority: Minor
>             Fix For: format-2.5.0
>
>
> [LogicalTypes.md in parquet-format|https://github.com/apache/parquet-format/blob/master/LogicalTypes.md] defines the the sort order for INTERVAL to be produced by sorting by the value of months, then days, then milliseconds with unsigned comparison.
> According to these rules, 1d0h0s > 0d48h0s, which is counter-intuitive and does not seem to have any practical uses. Unless somebody is aware of an actual use-case in which this makes sense, I think the sort order should be undefined instead. The [reference implementation in parquet-mr|https://github.com/apache/parquet-mr/blob/352b906996f392030bfd53b93e3cf4adb78d1a55/parquet-hadoop/src/main/java/org/apache/parquet/format/converter/ParquetMetadataConverter.java#L459] already considers the ordering to be unknown.



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