Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15609
Then, wouldn't the responsibility of type coercion be your own layer? I
guess this PR virtually mean every expression handled in `TypeCoercion` should
be fixed too. For example, I guess
```scala
Greatest(Seq(Literal(10, IntegerType), Literal("a", StringType))).eval()
```
wouldn't work too.
---
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
