[
https://issues.apache.org/jira/browse/KAFKA-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923586#comment-15923586
]
Gwen Shapira edited comment on KAFKA-4878 at 3/14/17 5:07 AM:
--------------------------------------------------------------
This is even worse in stand-alone mode because if you start it with bad config,
it won't start and you don't even have a REST API...
So far I ran into 4 users complaining about it, and 0.10.2.0 has only been out
for few weeks...
was (Author: gwenshap):
This is even worse in stand-alone mode because if you start it with bad config,
it won't start and you don't even have a REST API...
So far I ran into 4 users complaining about it, and 3.2 has only been out for a
week...
> Kafka Connect does not log connector configuration errors
> ---------------------------------------------------------
>
> Key: KAFKA-4878
> URL: https://issues.apache.org/jira/browse/KAFKA-4878
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Priority: Blocker
> Fix For: 0.10.2.1
>
>
> Currently, on connector configuration error, Kafka Connect (both distributed
> and stand alone) logs:
> org.apache.kafka.connect.runtime.rest.errors.BadRequestException: Connector
> configuration is invalid (use the endpoint `/{connectorType}/config/validate`
> to get a full list of errors)
> This is annoying because:
> 1. If I'm using stand-alone mode, I may have configured my connector via
> configuration file and I don't want to know about the REST API at all.
> 2. The output of validate is rather annoying
> What I'd like to see in the output is:
> 1. number of errors in my configuration
> 2. at least one error, preferably all of them
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
