Randall Hauch created KAFKA-6201:
------------------------------------
Summary: Provide more context in Kafka Connect REST error messages
Key: KAFKA-6201
URL: https://issues.apache.org/jira/browse/KAFKA-6201
Project: Kafka
Issue Type: Bug
Components: KafkaConnect
Affects Versions: 1.0.0
Reporter: Randall Hauch
It is possible that connectors with some characters in their names cause
problems, and these are being addressed in KAFKA-4827 and KAFKA-4930.
{code}
$ curl connect1:8083/connectors
[]
$ cat /usr/local/etc/connector-source-jdbc-properties.json {
"name" : "JDBC Source Connector",
"config" : {
"connector.class" : "io.confluent.connect.jdbc.JdbcSourceConnector",
"tasks.max" : "1",
"connection.url" : "jdbc:sqlite:/usr/local/lib/test.db",
"mode" : "incrementing",
"incrementing.column.name" : "id",
"topic.prefix" : "jdbc-"
}
}
$ curl -X POST -H "Content-Type: application/json" \--data
@/usr/local/etc/connector-source-jdbc-properties.json
http://connect1:8083/connectors
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /connectors. Reason:
<pre> Request failed.</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>
$ curl connect1:8083/connectors["JDBC Source Connector"]
{code}
This JIRA is about the meta point of error logging in general. The only
information returned from the REST call was {{Error 500}} with a poor message,
whereas what users really need is better error logging that guides users to
better understanding where the problem is. A much more usable message needs to
be provided in the return of the REST call.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
