Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15690
@tejasapatil I see your point. Implicit casting is powerful. Actually,
different languages have different preferences. I checked the related change
history of Spark SQL. I think we prefer to implicit casting in the Spark SQL
design. Especially after we introduce `TypeCollection` in the
https://github.com/apache/spark/pull/7202, the order of types defined in
`TypeCollection` also matters.
Question to @tejasapatil : have you hit the behavior differences between
Hive and Spark SQL caused by the implicit type casting? That means, although
the function signatures between Hive and Spark SQL are the same, the results
might be different due to the casted types are different.
---
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
