FYI it looks like this has to do with the representation of timestamps during
vectorized execution - timestamps are represented as a long value representing
nanoseconds since the epoch, thus the max timestamp value in that format is
2262-04-11
On Sep 22, 2014, at 4:13 PM, Peyman Mohajerian
So i found out more detail about this issue,
if in:
select cast('2999-12-31 23:59:59' as timestamp) from table;
if the table has 'orc' data, and you are using hive .13 and set
hive.vectorized.execution.enabled = true;
then this issue occurs, it maybe related to: hive-6656 i'm not certain of
that.
Hi Guys,
I Hive .13 for this conversion:
select cast('2999-12-31 23:59:59' as timestamp)
I get:
1830-11-23 00:50:51.580896768
up to around year 2199 it works fine, the work around is to convert the
string to int and then back to timestamp:
from_unixtime(unix_timestamp('2999-12-31
The point of over-flow is:
2262-04-11 20:00:00
if you go a second earlier it works fine:
2262-04-11 19:23:59
On Wed, Sep 10, 2014 at 5:38 PM, Peyman Mohajerian mohaj...@gmail.com
wrote:
Hi Guys,
I Hive .13 for this conversion:
select cast('2999-12-31 23:59:59' as timestamp)
I get:
