Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22144
After all, this is a bug and a regression from previous releases, like
other 1000 we've fixed before. According to the policy, we don't have to block
the current release because of it, and this bug
1. is a hive compatibility bug. Spark fails to run some Hive UDAFs
2. It fails the job instead of returning wrong result
3. the root cause is unknown
Thus, I think it's a non-blocker.
I looked into it more and I'm 90% sure this is caused by
https://issues.apache.org/jira/browse/SPARK-18186 . We should spend more time
on understanding how hive execute UDAF and fix the way we adapt it to Spark
aggregate function.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
