I don't see a problem in the result. Since you are using LEFT JOIN,
the NULLs are expected where there is no matching result in the right
table.
Hang Ruan 于2023年12月18日周一 09:39写道:
>
> Hi, David.
>
> The FLIP-377[1] is about this part. You could take a look at it.
>
> Best,
> Hang
>
> [1]
>
Hi, David.
The FLIP-377[1] is about this part. You could take a look at it.
Best,
Hang
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=276105768
Hang Ruan 于2023年12月17日周日 20:56写道:
> Hi, David.
>
> I think you are right that the value with NULL should not be returned if
>
Hi, David.
I think you are right that the value with NULL should not be returned if
the filter push down is closed.
Maybe you should explain this sql to make sure this filter not be pushed
down to the lookup source.
I see the configuration 'table.optimizer.source.predicate-pushdown-enabled'
Hi ,
I am working on FLINK-33365 which related to JDBC predicate pushdown. I want to
ensure that the same results occur with predicate pushdown as without. So I am
asking this question outside the pr / issue.
I notice the following behaviour for lookup joins without predicate pushdown. I
was