Github user mengxr commented on the issue:
https://github.com/apache/spark/pull/13872
@liancheng @rxin In the code, I didn't use UDF explicitly in a filter
expression. It is like the following:
~~~
filter b > 0
set a = udf(b)
filter a > 2
~~~
and the optimizer merged them into
~~~
filter udf(b) > 2 and b > 0
~~~
This could happen for any UDFs that throw exceptions. Are we assuming that
UDFs never throw exceptions?
The patch LGTM and I think we should merge it into 2.0.
---
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
