apupier commented on issue #821: URL: https://github.com/apache/camel-kafka-connector/issues/821#issuecomment-752128393
The ConfigDefs have null values. Consequently, I think that the table in documentation are generated with null displayed. Also the ConfigDef.hasDefaultValue() method returns true although the property has no default value. here it is planned that it would display "none": https://github.com/valdar/camel-kafka-connector/commit/c89703d5b19fa45ca30ec24e75fc6e92ed028439#diff-b35efa8afb4067fa0c36710e7cb3fe91b124cb6d1d9725bbcaf739c2af5c4e6bR33 but it is never the case as the ConfigDef.NO_DEFAULT_VALUE is never used. to avoid another layer of indirection, the COnfigDef are provided directly through the catalog for the "Basic configuration": https://github.com/valdar/camel-kafka-connector/blob/b07fd705f91eac57d7ba09e0959f9f2ec496e85c/camel-kafka-connector-catalog/src/main/java/org/apache/camel/kafkaconnector/catalog/CamelKafkaConnectorCatalog.java#L185-L191 Can you clarify what is the limitation with Camel? I do not understand what is limiting the fact to use the ConfigDef.NO_DEFAULT_VALUE in the config def. The Kafka properties reader is not returning null when asking for a property that is not explicitly set in case the ConfigDef.NO_DEFAULT_VALUE is set in the ConfigDef? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
