[
https://issues.apache.org/jira/browse/FLINK-27638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Spongebob updated FLINK-27638:
------------------------------
Attachment: image-2022-05-16-19-40-23-179.png
Description:
# register two table function named `FUNC_A` and `FUNC_B`
# left join with FUNC_A
# inner join with FUNC_B
# schedule the dml
after these steps, I found the task of FUNC_A keeped running but the task of
FUNC_B turned to be finished in serveral seconds. And I am not sure that the
unnormal task lead to empty output of the dml.
!image-2022-05-16-19-40-23-179.png!
was:
# regiseter one table function named `GET_STREAMING_MODEL_SINK_FILTER`
# create two complexible DML that both inner join with the table functioin and
they are all streaming tasks.
# schedule the two DML in one submission based on statementSet.
atfer these steps I found that the table function was run on one exclusive task
and it turned to be finished in serveral seconds. And the two DML had not any
output after the inner join with that table function.
Appendix `image-2022-05-16-19-08-25-477.png` shows the schedule graph of this
situation. And appendix `image-2022-05-16-19-08-50-286.png` shows the expected
graph when using table function.
!image-2022-05-16-19-08-25-477.png!
!image-2022-05-16-19-08-50-286.png!
> failed to join with table function
> ----------------------------------
>
> Key: FLINK-27638
> URL: https://issues.apache.org/jira/browse/FLINK-27638
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.14.3
> Reporter: Spongebob
> Priority: Major
> Attachments: image-2022-05-16-19-40-23-179.png
>
>
> # register two table function named `FUNC_A` and `FUNC_B`
> # left join with FUNC_A
> # inner join with FUNC_B
> # schedule the dml
> after these steps, I found the task of FUNC_A keeped running but the task of
> FUNC_B turned to be finished in serveral seconds. And I am not sure that the
> unnormal task lead to empty output of the dml.
> !image-2022-05-16-19-40-23-179.png!
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
