You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Krisztian Szucs (Jira)" <ji...@apache.org> on 2020/10/07 21:34:00 UTC

[jira] [Updated] (ARROW-9973) [Java] JDBC DateConsumer does not allow dates before epoch

     [ https://issues.apache.org/jira/browse/ARROW-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krisztian Szucs updated ARROW-9973:
-----------------------------------
    Fix Version/s: 2.0.0

> [Java] JDBC DateConsumer does not allow dates before epoch
> ----------------------------------------------------------
>
>                 Key: ARROW-9973
>                 URL: https://issues.apache.org/jira/browse/ARROW-9973
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 1.0.1
>            Reporter: Patrick Woody
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.0.0
>
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> DateConsumer seems to do an overflow check when converting from a SQL Date and sees if the TimeUnit.MILLISECONDS.toDays(<sql time>) is negative. This is how any date less than 1970-01-01 will be represented, so unfortunately the adapter breaks for these values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)