Github user wzhfy commented on the issue:
https://github.com/apache/spark/pull/16395
@ron8hu @rxin It seems we don't need logics for binary filter conditions
for date/timestamp types, because currently spark will always cast all relative
timestamp/data/string comparison into string comparisons. Thanks @cloud-fan for
indicating [the code
here](https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercion.scala#L317-L327)
Thus in tpcds benchmarks tests, filter estimation for date type is
unsupported:
```
[CBO] Unsupported filter condition: cast(d_date#119 as string) IN
(2000-06-30,2000-09-27,2000-11-17)
[CBO] Unsupported filter condition: (cast(d_date#63 as string) >=
2000-01-27)
...
```
---
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
