You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Wes McKinney (Jira)" <ji...@apache.org> on 2020/04/28 23:00:00 UTC
[jira] [Updated] (ARROW-8619) [C++] Use distinct Type::type values
for interval types
[ https://issues.apache.org/jira/browse/ARROW-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wes McKinney updated ARROW-8619:
--------------------------------
Description:
This is a breaking API change, but {{MonthIntervalType}} and {{DayTimeIntervalType}} are different data types (and have different value sizes, which is not true of timestamps) and thus should be distinguished in the same way that DATE32 / DATE64 are distinguished, or TIME32 / TIME64 are distinguished
This may nominally simplify function / kernel dispatch
was:This is a breaking API change, but {{MonthIntervalType}} and {{DayTimeIntervalType}} are different data types (and have different value sizes, which is not true of timestamps) and thus should be distinguished in the same way that DATE32 / DATE64 are distinguished, or TIME32 / TIME64 are distinguished
> [C++] Use distinct Type::type values for interval types
> -------------------------------------------------------
>
> Key: ARROW-8619
> URL: https://issues.apache.org/jira/browse/ARROW-8619
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Assignee: Wes McKinney
> Priority: Major
> Fix For: 1.0.0
>
>
> This is a breaking API change, but {{MonthIntervalType}} and {{DayTimeIntervalType}} are different data types (and have different value sizes, which is not true of timestamps) and thus should be distinguished in the same way that DATE32 / DATE64 are distinguished, or TIME32 / TIME64 are distinguished
> This may nominally simplify function / kernel dispatch
--
This message was sent by Atlassian Jira
(v8.3.4#803005)