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

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/04/01 12:04:00 UTC

[jira] [Comment Edited] (FLINK-26989) Fix the potential lost of secondary resource when watching a namespace

    [ https://issues.apache.org/jira/browse/FLINK-26989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515886#comment-17515886 ] 

Aitozi edited comment on FLINK-26989 at 4/1/22 12:03 PM:
---------------------------------------------------------

If there's one namespace, the eventsource do not duplicated for the same type, so not a bug, closing~


was (Author: aitozi):
If there's a namespace, the eventsource do not duplicated for the same type, so not a bug, closing~

> Fix the potential lost of secondary resource when watching a namespace
> ----------------------------------------------------------------------
>
>                 Key: FLINK-26989
>                 URL: https://issues.apache.org/jira/browse/FLINK-26989
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Aitozi
>            Priority: Major
>              Labels: pull-request-available
>
> The event source is register under the name of namespace when watching namespace is not empty, But when we get from the context, we use the different condition, It may make it miss the target event source



--
This message was sent by Atlassian Jira
(v8.20.1#820001)