[jira] [Closed] (FLINK-11435) Different jobs same consumer group are treated as separate groups

["Aljoscha Krettek (JIRA)" <ji...@apache.org>]

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

Aljoscha Krettek closed FLINK-11435.
------------------------------------
    Resolution: Not A Problem

As [~elevy] mentioned, this is a core design decision of the Flink Kafka Consumer. If we want to have this functionality, this would require adding a new Kafka consumer with the alternative behaviour. It couldn't be done as a change of the current consumer. Since that is a bigger thing it would require at least a discussion on the dev ML, probably a FLIP (https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals).

I'm closing for now because I agree with Elias that we can't consider this a bug.

> Different jobs same consumer group are treated as separate groups
> -----------------------------------------------------------------
>
>                 Key: FLINK-11435
>                 URL: https://issues.apache.org/jira/browse/FLINK-11435
>             Project: Flink
>          Issue Type: Bug
>          Components: Kafka Connector
>    Affects Versions: 1.7.1
>         Environment: kafka consumer
>            Reporter: Avi Levi
>            Priority: Major
>
> deploying two jobs with the same consumer group id, still treated as different consumer groups. This behavior does not comply with kafka expectations. Same consumer group ids should be treated as the same group this will enable deploying more jobs (specially if they are stateless ) on demand and it also how normal consumer groups behave. 
> reproduce :
> deploy the same job twice - both jobs consumes the same message although they share the same consumer id



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)