Github user adrian-wang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7643#discussion_r35724130
--- 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 --
that's because hive support passing a numeric value as the first parameter
of utc_timestamp, and act just like casting this numeric value to Timestamp
first. I didn't check other functions that accepts timestamp, but I think they
should also work in this way, will check soon.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
