comphead commented on issue #1929:
URL:
https://github.com/apache/datafusion-comet/issues/1929#issuecomment-3006128645
> I don't think this is a bug. Spark likely optimizes the array_contains
expression during planning time and replaces it with a boolean literal?
>
> ```
> checkSparkAnswerAndOperator(spark.sql("SELECT array_contains(cast(array()
as array<int>), _2) FROM t1"))
> ```
>
> See comment [#1923
(comment)](https://github.com/apache/datafusion-comet/pull/1923#issuecomment-3002328767)
for more information
Thanks @andygrove that makes sense. I also checked
```
checkSparkAnswerAndOperator(
spark.sql("SELECT array_contains((CASE WHEN _2 =_3 THEN array()
END), _4) FROM t1"));
```
But I still can see the fallback 🤔
--
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: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
