GitHub user original-brownbear opened a pull request:
https://github.com/apache/kafka/pull/2722
KAFKA-4878: Improved Invalid Connect Config Error Message
Addresses for https://issues.apache.org/jira/browse/KAFKA-4878
* Adjusted the error message to explicitly state errors and their number
* Dried up the logic for generating the message between standalone and
distributed
Example
messed up two config keys in the file source config:
````
namse=local-file-source
connector.class=FileStreamSource
tasks.max=1
fisle=test.txt
topic=connect-test
```
Produces:
```
[2017-03-22 08:57:11,896] ERROR Stopping after connector error
(org.apache.kafka.connect.cli.ConnectStandalone:99)
java.util.concurrent.ExecutionException:
org.apache.kafka.connect.runtime.rest.errors.BadRequestException: Connector
configuration is invalid and contains the following 2 error(s):
Missing required configuration "file" which has no default value.
Missing required configuration "name" which has no default value.
You can also find the above list of errors at the endpoint
`/{connectorType}/config/validate`
```
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/original-brownbear/kafka KAFKA-4878
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2722.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 #2722
----
commit 0135ed6a3f1399ecefd2f477c9c82c7830313adc
Author: Armin Braun <[email protected]>
Date: 2017-03-22T07:20:11Z
KAFKA-4878: Improved Error Messages for Broken Connect Config
commit 7790532b8c43048197256b92e9970270e4fe1152
Author: Armin Braun <[email protected]>
Date: 2017-03-22T07:58:49Z
KAFKA-4878: Improved Error Message Text
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
