Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/7643#discussion_r35897268
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/HiveTypeCoercion.scala
---
@@ -753,6 +753,9 @@ object HiveTypeCoercion {
case (DateType, TimestampType) => Cast(e, TimestampType)
case (TimestampType, DateType) => Cast(e, DateType)
+ // Implicit cast for functions like utc_timestamp
+ case (_: NumericType, TimestampType) => Cast(e, TimestampType)
--- End diff --
Currently, we cast numeric type to timestamp type in different ways, for
example, byte/short/int/long will be milliseconds, decimal/float/double will be
seconds.
Also, we use seconds when we turn timestamp into long.
When utc_timestamp() work with long, is it used as seconds or milliseconds ?
---
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]
