Github user marmbrus commented on the issue:
https://github.com/apache/spark/pull/17087
There appears to have been some code drift (as `GeneratePredicate` and
`InterpretedPredicate` both used to return a class that inherited from a common
interface), but I don't think its hard to just isolate the fault handling in
`newPredicate`.
Just fix
[InterpretedPredicate](https://github.com/apache/spark/blob/9b7a03f15ac45e5f7dcf118d1e7ce1556339aa46/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala)
to actually return a `Predicate` rather than a bare lambda function. The code
there already handles binding and evaluation.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
