[
https://issues.apache.org/jira/browse/FLINK-31275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695756#comment-17695756
]
Jark Wu edited comment on FLINK-31275 at 3/2/23 3:03 PM:
---------------------------------------------------------
Hi [~zjureel], feel free to create FLIP and start a discussion in dev ML. But
according to the community contribution guideline[1], issues can be assigned
only if there is consensus on the approach.
[1]:
https://flink.apache.org/how-to-contribute/contribute-code/#code-contribution-process
was (Author: jark):
Hi [~zjureel], feel free to create FLIP and start a discussion in dev ML.
According to the community contribution guideline, issue can be assigned only
if there is consensus on the approach.
> Generate planner id in planner
> ------------------------------
>
> Key: FLINK-31275
> URL: https://issues.apache.org/jira/browse/FLINK-31275
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.18.0
> Reporter: Shammon
> Priority: Major
>
> Currently flink generates job id in `JobGraph` which can identify a job. On
> the other hand, flink create source/sink table in planner. We need to create
> relations between source and sink tables for the job, so we should generate a
> planner id in planner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
