[
https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Randall Hauch updated KAFKA-5412:
---------------------------------
Description:
With the latest 0.11.1.0-SNAPSHOT it happens that the Kafka Connect example
using connect-console-sink/source.properties doesn't work anymore because the
needed "file" property isn't found. This is because the underlying used
FileStreamSink/Source connector and task has defined a ConfigDef with "file" as
mandatory parameter. In the case of console example we want to have file=null
so that stdin and stdout are used.
One possible solution and workaround is set "file=" inside the provided
connect-console-sink/source.properties. The other one could be modify the
FileStreamSink/Source source code in order to remove the "file" definition from
the ConfigDef.
was:
Hi,
with the latest 0.11.1.0-SNAPSHOT it happens that the Kafka Connect example
using connect-console-sink/source.properties doesn't work anymore because the
needed "file" property isn't found.
This is because the underlying used FileStreamSink/Source connector and task
has defined a ConfigDef with "file" as mandatory parameter. In the case of
console example we want to have file=null so that stdin and stdout are used.
One possible solution and workaround is set "file=" inside the provided
connect-console-sink/source.properties.
The other one could be modify the FileStreamSink/Source source code in order to
remove the "file" definition from the ConfigDef.
> Using connect-console-sink/source.properties raises an exception related to
> "file" property not found
> -----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5412
> URL: https://issues.apache.org/jira/browse/KAFKA-5412
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 0.10.2.1
> Reporter: Paolo Patierno
> Fix For: 0.11.1.0
>
>
> With the latest 0.11.1.0-SNAPSHOT it happens that the Kafka Connect example
> using connect-console-sink/source.properties doesn't work anymore because the
> needed "file" property isn't found. This is because the underlying used
> FileStreamSink/Source connector and task has defined a ConfigDef with "file"
> as mandatory parameter. In the case of console example we want to have
> file=null so that stdin and stdout are used.
> One possible solution and workaround is set "file=" inside the provided
> connect-console-sink/source.properties. The other one could be modify the
> FileStreamSink/Source source code in order to remove the "file" definition
> from the ConfigDef.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
