Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8400#issuecomment-134674552
The result you posted for Spark is totally wrong (you can't get the
timestamp back after one round trip), fortunately this is a fake alarm :)
For the Hive one, it bad but not wrong (different rounding method, you can
still read the timestamp back).
In general, maybe using Julian day here is the root of bad things, use
signed integer for number of days since epoch should be enough (could be
negative).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]