Github user petermaxlee commented on the issue:
https://github.com/apache/spark/pull/14389
@HyukjinKwon FWIW I don't think it makes sense to handle everything except
greatest/least. It also does not make sense to automatically coerce from
decimal to double type for these two functions.
The decimal truncation problem described in SPARK-16646 seems orthogonal to
this. It would be better if we don't need to worry about truncation (e.g. with
unlimited decimal or with precision always double the size of scale), but I
don't think that should impact what type greatest/least use.
---
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]
