You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2021/10/20 02:22:00 UTC

[jira] [Closed] (FLINK-24562) YarnResourceManagerDriverTest should not use ContainerStatusPBImpl.newInstance

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

Xintong Song closed FLINK-24562.
--------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

Fixed in
- master (1.15): a08e7c6577557dce874b30df9c8b3692d9575282

> YarnResourceManagerDriverTest should not use ContainerStatusPBImpl.newInstance
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-24562
>                 URL: https://issues.apache.org/jira/browse/FLINK-24562
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.14.0
>            Reporter: Feifan Wang
>            Assignee: Feifan Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> In YarnResourceManagerDriverTest, we create ContainerStatus with the static method ContainerStatusPBImpl{{.newInstance}}, which is annotated as private and unstable.
> Although this method is still available in the latest version of yarn, some third-party versions of yarn may modify it. In fact, this method was modified in the internal version provided by our yarn team, which caused flink-1.14.0 to fail to compile.
> Moreover, there is already an org.apache.flink.yarn.TestingContainerStatus, I think we should use it directly.
>  



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