DateConsumer seems to do an overflow check when converting from a SQL Date and sees if the TimeUnit.MILLISECONDS.toDays() is negative. This is how any date less than 1970-01-01 will be represented, so unfortunately the adapter breaks for these values.
Reporter: Patrick Woody
PRs and other links:
Note: This issue was originally created as ARROW-9973. Please see the migration documentation for further details.
DateConsumer seems to do an overflow check when converting from a SQL Date and sees if the TimeUnit.MILLISECONDS.toDays() is negative. This is how any date less than 1970-01-01 will be represented, so unfortunately the adapter breaks for these values.
Reporter: Patrick Woody
PRs and other links:
Note: This issue was originally created as ARROW-9973. Please see the migration documentation for further details.