You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Ewen Cheslack-Postava (JIRA)" <ji...@apache.org> on 2016/06/09 21:22:20 UTC

[jira] [Commented] (KAFKA-3814) Connectors should be able to know their name

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

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

[~rhauch] Is this true? I would think you could get it out of the configuration you're passed in start()? It might still make sense to include this automatically (and tasks might want to know their task ID too), but the info you want might already be available.

> Connectors should be able to know their name
> --------------------------------------------
>
>                 Key: KAFKA-3814
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3814
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.1
>            Reporter: Randall Hauch
>            Assignee: Ewen Cheslack-Postava
>            Priority: Minor
>
> Currently a connector implementation does not have access to the unique name that Kafka Connect framework uses for each connector. For example, the [http://docs.confluent.io/3.0.0/connect/userguide.html#rest-interface|REST API] of the workers make use of this name.
> The connectors could use this name in a number of ways, not the least of which is using the name in log messages to help the administrator correlate messages with configured connectors.
> It is possible to work around this by using an additional configuration property, although it is not ideal since the property value and connector name might diverge, making it harder to correlate the two.



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