Description
After HIVE-3454 is fixed, we will have correct behavior of converting int to timestamp. While the customers are using such incorrect behavior for so long, better to make it configurable so that in one release, it will default to old/inconsistent way and the next release will default to new/consistent way. And then we will deprecate it.
Attachments
Attachments
Issue Links
- depends upon
-
HIVE-3454 Problem with CAST(BIGINT as TIMESTAMP)
- Closed
- is depended upon by
-
HIVE-10212 When timestamp is converted to bigint, it's always interpreted as seconds while bigint to timestamp is in milliseconds.
- Resolved
- is related to
-
HIVE-11168 Followup on HIVE-9917, set the default value of hive.int.timestamp.conversion.in.seconds to true
- Open