dilipbiswal commented on a change in pull request #24209: [SPARK-27255][SQL]
Aggregate functions should not be allowed in WHERE
URL: https://github.com/apache/spark/pull/24209#discussion_r270036188
##########
File path:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
##########
@@ -172,13 +172,17 @@ trait CheckAnalysis extends PredicateHelper {
failAnalysis("Null-aware predicate sub-queries cannot be used in
nested " +
s"conditions: $condition")
+ case f @ Filter(condition, _) if
PlanHelper.specialExpressionInUnsupportedOperator(f) =>
Review comment:
@cloud-fan I thought, having a targeted error message for the user would be
better. If we do it generically, we would say "Filter" instead of "WHERE
clause", right ? Should i handle for Filter here and have a general catcher as
the last case statement to issue a generic error message like "The operator
xxxx contains an unsupported expression type"?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
