[jira] [Updated] (FLINK-16180) Replacing vertexExecution in ScheduledUnit with executionVertexID

["Zhu Zhu (Jira)" <ji...@apache.org>]

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

Zhu Zhu updated FLINK-16180:
----------------------------
        Parent: FLINK-15626
    Issue Type: Sub-task  (was: Improvement)

> Replacing vertexExecution in ScheduledUnit with executionVertexID
> -----------------------------------------------------------------
>
>                 Key: FLINK-16180
>                 URL: https://issues.apache.org/jira/browse/FLINK-16180
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.11.0
>            Reporter: Zhu Zhu
>            Assignee: Zhu Zhu
>            Priority: Major
>             Fix For: 1.11.0
>
>
> {{ScheduledUnit#vertexExecution}} is nullable but {{ProgrammedSlotProvider}} requires it to be non-null to work. This makes {{ProgrammedSlotProvider}} not able to be used by new scheduler tests since {{vertexExecution}} is never set in the new scheduler code path. It blocks us from reworking tests which are based legacy scheduling to base on the new scheduler.
> I would propose to replace vertexExecution with a non-null executionVertexID.
> This change would not break anything since {{vertexExecution}} is mainly used by {{ProgrammedSlotProvider}} in tests and logging in production. And the log would be broken if it is null.
> This would also fix a potential bug, as reported in FLINK-16145.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)