You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Uwe Korn (Jira)" <ji...@apache.org> on 2019/11/07 21:37:00 UTC
[jira] [Commented] (ARROW-7084) [C++] ArrayRangeEquals should
check for full type equality?
[ https://issues.apache.org/jira/browse/ARROW-7084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969576#comment-16969576 ]
Uwe Korn commented on ARROW-7084:
---------------------------------
It was an oversight when fixing ARROW-2567 , we should also fix ArrayRangeEquals.
> [C++] ArrayRangeEquals should check for full type equality?
> ------------------------------------------------------------
>
> Key: ARROW-7084
> URL: https://issues.apache.org/jira/browse/ARROW-7084
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Reporter: Micah Kornfield
> Priority: Major
>
> It looks like ArrayRangeEquals in compare.cc only checks type IDs before doing comparison actual values. This is inconsistent with ArrayEquals which checks for type equality and also seems incorrect for cases like Decimal128.
>
> I presume this was an oversight when fixing ARROW-2567 but maybe it was intentional?
> [~uwe]?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)