[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't work on 64-bit integers

2019-06-19 Thread Brian Hulette (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARROW-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867816#comment-16867816
 ] 

Brian Hulette commented on ARROW-2797:
--

Maybe if we only support this when we have BigInt it wouldn't be that big of a 
change?

> [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
>Assignee: 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)

[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't work on 64-bit integers

2019-06-12 Thread Wes McKinney (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARROW-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16862299#comment-16862299
 ] 

Wes McKinney commented on ARROW-2797:
-

Any thoughts about this for 0.14.0? [~bhulette] [~paul.e.taylor]

> [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
>Assignee: Brian Hulette
>Priority: Major
> Fix For: 0.14.0
>
>
> 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)

[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't work on 64-bit integers

2018-08-07 Thread Cameron Davison (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARROW-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571541#comment-16571541
 ] 

Cameron Davison commented on ARROW-2797:


Just to keep in mind this will also affect Int128

> [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)

[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't work on 64-bit integers

2018-08-07 Thread nevi_me (JIRA) 


[ 
https://issues.apache.org/jira/browse/ARROW-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571302#comment-16571302
 ] 

nevi_me commented on ARROW-2797:


There's also 
[https://github.com/apache/arrow/issues/2358|ttps://github.com/apache/arrow/issues/2358]
 which looks like the same issue.

> [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)

[jira] [Commented] (ARROW-2797) [JS] comparison predicates don't work on 64-bit integers

2018-07-06 Thread Taras Novak (JIRA) 


[ 
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)