[
https://issues.apache.org/jira/browse/FLINK-32471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-32471:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> IS_NOT_NULL can add to SUITABLE_FILTER_TO_PUSH
> ----------------------------------------------
>
> Key: FLINK-32471
> URL: https://issues.apache.org/jira/browse/FLINK-32471
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Reporter: grandfisher
> Priority: Major
> Labels: pull-request-available, stale-major
>
> According to FLINK-31273:
> The reason for the error is that other filters conflict with IS_NULL, but in
> fact it won't conflict with IS_NOT_NULL, because operators in
> SUITABLE_FILTER_TO_PUSH such as 'SqlKind.GREATER_THAN' has an implicit
> filter 'IS_NOT_NULL' according to SQL Semantics.
>
> So we think it is feasible to add IS_NOT_NULL to the SUITABLE_FILTER_TO_PUSH
> list.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
