[jira] [Commented] (KAFKA-3524) ConnectorTaskId should also also include cluster id

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

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

Ewen Cheslack-Postava commented on KAFKA-3524:
----------------------------------------------

[~fpj] Can you explain the use case a bit more? I get that there might be reasons to identify by (cluster, task, id) outside of connect, but ConnectorTaskId is currently an implementation detail in the connect runtime package. Is there some use within connect where you need the cluster ID as well, or are you thinking about using this outside of Connect?

> ConnectorTaskId should also also include cluster id
> ---------------------------------------------------
>
>                 Key: KAFKA-3524
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3524
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>            Reporter: Flavio Junqueira
>            Assignee: Ewen Cheslack-Postava
>
> ConnectorTaskId currently uses the connector name and the task number to give a unique id to a task. This id is unique within a connect cluster, but it might not be unique across clusters. If I want to uniquely identify connector tasks across clusters, then I need to also use the cluster name as part of the id. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)