You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Weston Pace (Jira)" <ji...@apache.org> on 2022/02/05 00:57:00 UTC
[jira] [Updated] (ARROW-15581) [C++] Add proper support for Substrait intervals
[ https://issues.apache.org/jira/browse/ARROW-15581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Weston Pace updated ARROW-15581:
--------------------------------
Description:
The Arrow Substrait consumer does not currently support functions on intervals. This is because the Substrait deserializer currently asserts that all information must be round trippable and it errs on the side of rejecting plans before allowing a plan that could be correct consumed but not round tripped.
This affects interval types because, for example, the substrait interval 1 year 12 months would be converted to the substrait interval 2 years after a round trip.
To resolve this the current implementation encodes intervals as fixed length lists of numbers which we cannot do any kind of temporal math on.
was:
The Arrow Substrait consumer does not currently support functions on intervals. This is because the Substrait deserializer currently asserts that all information must be round trippable and it errs on the side of rejecting plans before allowing a plan that could be correct consumed but not round tripped.
This affects interval types because, for example, the substrait interval 1 year 12 months would be converted to the substrait interval 2 years after a round trip.
To resolve this the current implementation encodes intervals as fixed length lists of numbers which we cannot do any kind of datetime math on.
> [C++] Add proper support for Substrait intervals
> ------------------------------------------------
>
> Key: ARROW-15581
> URL: https://issues.apache.org/jira/browse/ARROW-15581
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Weston Pace
> Priority: Major
> Labels: substrait
>
> The Arrow Substrait consumer does not currently support functions on intervals. This is because the Substrait deserializer currently asserts that all information must be round trippable and it errs on the side of rejecting plans before allowing a plan that could be correct consumed but not round tripped.
> This affects interval types because, for example, the substrait interval 1 year 12 months would be converted to the substrait interval 2 years after a round trip.
> To resolve this the current implementation encodes intervals as fixed length lists of numbers which we cannot do any kind of temporal math on.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)