GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/8606
[SPARK-10439] [sql] Add bound checks to DateTimeUtils.
There were a couple of places where Spark SQL would silently truncate
data if certain timestamps were provided.
In a couple of other places, the way to calculate Julian day-based
timestamps was changed a little so that Spark writes data that is
friendlier to Hive; mostly, Hive does not like very much when
the data has negative values for either the days or nanos part,
so avoid those.
The values that trigger these use cases are very uncommon (very large
values in either end of the spectrum), so this shouldn't really affect
any existing applications.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vanzin/spark SPARK-10439
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/8606.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #8606
----
commit ffe39e4a1c31f606caeed3f3e193e9945b7e8923
Author: Marcelo Vanzin <[email protected]>
Date: 2015-09-04T18:30:50Z
[SPARK-10439] [sql] Add bound checks to DateTimeUtils.
There were a couple of places where Spark SQL would silently truncate
data if certain timestamps were provided.
In a couple of other places, the way to calculate Julian day-based
timestamps was changed a little so that Spark writes data that is
friendlier to Hive; mostly, Hive does not like very much when
the data has negative values for either the days or nanos part,
so avoid those.
The values that trigger these use cases are very uncommon (very large
values in either end of the spectrum), so this shouldn't really affect
any existing applications.
----
---
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]
