aokolnychyi commented on code in PR #51146:
URL: https://github.com/apache/spark/pull/51146#discussion_r2159761195
##########
sql/catalyst/src/main/java/org/apache/spark/sql/connector/expressions/filter/AlwaysNull.java:
##########
@@ -0,0 +1,32 @@
+package org.apache.spark.sql.connector.expressions.filter;
+
+import org.apache.spark.annotation.Evolving;
+import org.apache.spark.sql.connector.expressions.Literal;
+import org.apache.spark.sql.types.DataType;
+import org.apache.spark.sql.types.DataTypes;
+
+/**
+ * A predicate that always evaluates to {@code null}.
+ *
+ * @since 4.1.0
+ */
+@Evolving
+public final class AlwaysNull extends Predicate implements Literal<Boolean> {
Review Comment:
I generally don't mind adding AlwaysNull but I am not sure there is value in
allowing CHECK (null), to be honest. I know some databases accept it but it
seems useless. Are there databases that reject or ignore these? Or most
databases support them?
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
