[ 
https://issues.apache.org/jira/browse/FLINK-36064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Junrui Li updated FLINK-36064:
------------------------------
    Description: 
Currently, the REST API between clients and operator coordinators relies on the 
operator ID to send requests to the Job Manager (JM) for querying results. 
However, with the introduction of Stream Graph submission, the Job Graph will 
be compiled and generated within the JM, preventing the client from accessing 
the operator ID.

To address this issue, we modify the REST API for communication between clients 
and operator coordinators by removing the dependency on operatorID and 
transitioning to a client-defined {{{}String operatorUid{}}}.

  was:
Currently, the CollectResultIterator relies on the operator ID to send REST 
requests to the JM for querying results. However, with the introduction of 
Stream Graph submission, the Job Graph will be compiled and generated within 
the JM, resulting in the client being unable to access the operator ID.

To resolve this issue, we intend to refactor CollectResultIterator to remove 
its dependency on the operator ID and utilize an alternative UUID instead.


> Refactor CollectResultIterator to eliminate dependency on OperatorID
> --------------------------------------------------------------------
>
>                 Key: FLINK-36064
>                 URL: https://issues.apache.org/jira/browse/FLINK-36064
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>            Reporter: Junrui Li
>            Assignee: Junrui Li
>            Priority: Major
>              Labels: pull-request-available
>
> Currently, the REST API between clients and operator coordinators relies on 
> the operator ID to send requests to the Job Manager (JM) for querying 
> results. However, with the introduction of Stream Graph submission, the Job 
> Graph will be compiled and generated within the JM, preventing the client 
> from accessing the operator ID.
> To address this issue, we modify the REST API for communication between 
> clients and operator coordinators by removing the dependency on operatorID 
> and transitioning to a client-defined {{{}String operatorUid{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to