You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/22 01:51:12 UTC

[jira] [Commented] (KAFKA-3605) Connector REST endpoint allows incorrectly overriding the connector name

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

ASF GitHub Bot commented on KAFKA-3605:
---------------------------------------

GitHub user ewencp opened a pull request:

    https://github.com/apache/kafka/pull/1253

    KAFKA-3605: Return error if connector config includes mismatching connector name.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ewencp/kafka kafka-3605-connector-name-mismatch

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1253.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1253
    
----
commit 1ed45ec3e93252c15e905de9cfc14630303711b8
Author: Ewen Cheslack-Postava <me...@ewencp.org>
Date:   2016-04-21T23:48:37Z

    KAFKA-3605: Return error if connector config includes mismatching connector name.

----


> Connector REST endpoint allows incorrectly overriding the connector name
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-3605
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3605
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.9.0.1
>            Reporter: Ewen Cheslack-Postava
>            Assignee: Ewen Cheslack-Postava
>            Priority: Blocker
>             Fix For: 0.10.0.0
>
>
> If you PUT a connector config and it includes a connector name that doesn't match the URL, the request will succeed. It obviously shouldn't since the wrong connector name will be included. This should trigger an error in the 400 range instead.



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