Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/19389
Generally, the current type inference/coercion rules are messy and random.
We have to seriously revisit our type coercion.
After thinking it more, I think this change in this PR is pretty risky. It
just introduces new type inference behaviors, although I do not like the
previous one neither. These changes could easily cause new regression when our
users upgrading their Spark versions.
For making the migration more smooth, my general proposal is to introduce a
conf for each one when we change something like this, if we believe this is a
bug fix. Remove or deprecate the internal conf in the next release (or after a
few releases) if nobody raises the issue after a major release (around half a
year).
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
