Github user ueshin commented on the issue: https://github.com/apache/spark/pull/13909 @cloud-fan Hmm, I didn't mean we don't trust the source side. Currently we DO validate the null regardless of `allowNull` value. The difference by the `allowNull` is setting null or throwing an exception. I think which we should do when `containsNull == false` is throwing an exception. (Anyway, `eval.isNull` of most of children will be `"false"` when `nullable == false`, so Janino will remove the `$isNullAssignment` clause.
--- 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