[
https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043018#comment-16043018
]
Randall Hauch commented on KAFKA-5412:
--------------------------------------
I believe the proper correction would be to add a null default value to the
ConfigDef in FileStreamSink/Source. When no default value is provided, this
means that the value is required. Clearly the FileStreamSink/Source is able to
handle the "file" configuration not being specified, since it then works on the
standard ouptut/input, respectively.
> 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.11.1.0
> Reporter: Paolo Patierno
>
> 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 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.
> What do you think ?
> I can provide a PR for that.
> Thanks,
> Paolo.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
