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/05/04 03:06:12 UTC

[jira] [Resolved] (KAFKA-3654) Config validation should validate both common and connector specific configurations

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

Ewen Cheslack-Postava resolved KAFKA-3654.
------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.1.0

Issue resolved by pull request 1313
[https://github.com/apache/kafka/pull/1313]

> Config validation should validate both common and connector specific configurations
> -----------------------------------------------------------------------------------
>
>                 Key: KAFKA-3654
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3654
>             Project: Kafka
>          Issue Type: Bug
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.0
>            Reporter: Liquan Pei
>            Assignee: Liquan Pei
>             Fix For: 0.10.1.0, 0.10.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Right now if you call the validate endpoint with a config that has an invalid value for one of the common connector configs from here, we do not get any config/validation info for connector implementation configs. We would like to do validation of both the common config and connector specific config.



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