[
https://issues.apache.org/jira/browse/FLINK-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hequn Cheng updated FLINK-11310:
--------------------------------
Description:
In FLINK-10474, we force translate IN into a predicate to avoid translating to
a JOIN. In addition, we add a Rule to convert the predicates back to IN so that
we can generate code using a HashSet for the IN.
However, FLINK-10474 only takes Filter into consideration. It would be great to
also convert predicates in Project to IN. It not only will improve the
performance for the Project, but also will avoid the problem raised in
FLINK-11308, as all predicates will be converted into one IN expression.
was:
In FLINK-10474, we force translate IN into a predicate to avoid translating to
a JOIN. In addition, we add a Rule to convert the predicates back to IN so that
we can generate code using a HashSet for the IN.
However, FLINK-10474 only takes Filter into consideration. It would be great to
also convert predicates in Project to IN. It not only will improve the
performance for the Project, but also will address the problem raised in
FLINK-11308, as all predicates will be converted into one IN expression.
> Convert predicates to IN or NOT_IN for Project
> ----------------------------------------------
>
> Key: FLINK-11310
> URL: https://issues.apache.org/jira/browse/FLINK-11310
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Hequn Cheng
> Assignee: Hequn Cheng
> Priority: Major
>
> In FLINK-10474, we force translate IN into a predicate to avoid translating
> to a JOIN. In addition, we add a Rule to convert the predicates back to IN so
> that we can generate code using a HashSet for the IN.
> However, FLINK-10474 only takes Filter into consideration. It would be great
> to also convert predicates in Project to IN. It not only will improve the
> performance for the Project, but also will avoid the problem raised in
> FLINK-11308, as all predicates will be converted into one IN expression.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
