You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Taras Novak (JIRA)" <ji...@apache.org> on 2018/07/06 18:06:00 UTC
[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't
work on 64-bit integers
[ https://issues.apache.org/jira/browse/ARROW-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16535191#comment-16535191 ]
Taras Novak commented on ARROW-2797:
------------------------------------
basically, we'd like to compare ints or find a better way to do this for Timestamps without conversion to Date for 100+K records. Probably same desire applies for other 64 bit packed ints.
the origins of this request: [https://beta.observablehq.com/@randomfractals/apache-arrow]
I'd like to optimize that without unpacking millisecs from epoch to dates.
Create new Timestamp from a Date example with arrow could probably do a trick for this perf. tuning bit, but I suspect there is more we should unpack there.
Thanks to [~bhulette] for collabo on this bit!
> [JS] comparison predicates don't work on 64-bit integers
> --------------------------------------------------------
>
> Key: ARROW-2797
> URL: https://issues.apache.org/jira/browse/ARROW-2797
> Project: Apache Arrow
> Issue Type: Bug
> Components: JavaScript
> Affects Versions: JS-0.3.1
> Reporter: Brian Hulette
> Priority: Major
>
> The 64-bit integer vector {{get}} function returns a 2-element array, which doesn't compare propery in the comparison predicates. We should special case the comparisons for 64-bit integers and timestamps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)