[JS] comparison predicates don't work on 64-bit integers

[asfimport]

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.

Reporter: Brian Hulette / @TheNeuralBit

_{Note: This issue was originally created as ARROW-2797. Please see the migration documentation for further details.}

[asfimport]

Taras Novak:
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 start/end filter example instead with arrow could probably do a trick for this perf. tuning bit, but I suspect there is more we should unpack there.

Thanks to @TheNeuralBit for collabo on this bit!

 

[asfimport]

Neville Dipale / @nevi-me:
There's also apache/arrow#2358 which looks like the same issue.

[asfimport]

Cameron Davison:
Just to keep in mind this will also affect Int128

[asfimport]

Wes McKinney / @wesm:
Any thoughts about this for 0.14.0? @TheNeuralBit [~paul.e.taylor]

[asfimport]

Brian Hulette / @TheNeuralBit:
Maybe if we only support this when we have BigInt it wouldn't be that big of a change?

[asfimport]

Todd Farmer / @toddfarmer:
This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.