Skip to content

Commit 63d0c39

Browse files
author
Marcelo Vanzin
committed
Revert to previous bounds for timestamp values.
1 parent 196ba9e commit 63d0c39

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/util/DateTimeUtils.scala

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -59,15 +59,9 @@ object DateTimeUtils {
5959

6060
// Constants defining the allowed ranges for timestampts that fit in parquet files. Mostly
6161
// used by tests to avoid duplication.
62-
//
63-
// -62135740800000L is the number of milliseconds before January 1, 1970, 00:00:00 GMT
64-
// for "0001-01-01 00:00:00.000000". We need to find a
65-
// number that is greater or equals to this number as a valid timestamp value.
66-
//
67-
// 253402329599999L is the the number of milliseconds since
68-
// January 1, 1970, 00:00:00 GMT for "9999-12-31 23:59:59.999999".
69-
private[spark] final val MIN_TIMESTAMP: Long = -62135740800000L
70-
private[spark] final val MAX_TIMESTAMP: Long = 253402329599999L
62+
private[spark] final val MIN_TIMESTAMP: Long =
63+
-(DateTimeUtils.JULIAN_DAY_OF_EPOCH * DateTimeUtils.SECONDS_PER_DAY * 1000)
64+
private[spark] final val MAX_TIMESTAMP: Long = java.lang.Long.MAX_VALUE / 1000
7165

7266
// Java TimeZone has no mention of thread safety. Use thread local instance to be safe.
7367
private val threadLocalLocalTimeZone = new ThreadLocal[TimeZone] {

0 commit comments

Comments
 (0)