GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/14439
[SPARK-16714][SPARK-16735][SPARK-16646] array, map, greatest, least's type
coercion should handle decimal type
## What changes were proposed in this pull request?
`array`, `map`, `greatest`, `least` should not fail if its arguments are
decimal types, even if the wider type of these decimal types exceed system
limitation and we have to truncate.
fix `array` and `map` by using `findWiderCommonType` to get the wider type.
fix `greatest` and `least` by add a `findWiderTypeWithoutStringPromotion`,
which provides similar semantic of `findWiderCommonType`, but without string
promotion.
## How was this patch tested?
new tests in `TypeCoersionSuite`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark bug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/14439.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #14439
----
commit 95f0866b9ca82e117b7454a1d72706618f7db4f4
Author: Wenchen Fan <wenc...@databricks.com>
Date: 2016-08-01T14:23:50Z
array, map, greatest, least's type coercion should handle decimal type
----
---
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
