[
https://issues.apache.org/jira/browse/KAFKA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417295#comment-13417295
]
Jay Kreps commented on KAFKA-181:
---------------------------------
Here are a few other facilities it would be nice to have if we were adding a
generic config helper class:
# It would also be nice to have a facility to support aliases for backwards
compatibility. Say we introduce a property log.retention.size and later realize
that is inconsistent with the other properties which explicitly give the units.
It would be nice to change the name to log.retention.size.bytes as the official
name but still retain the old name for compatability. Of course this can be
done manually, but maybe could be done better in the helper class.
# It would be nice to require an official documentation field.
# It would be nice to have a way to dump out all configs used, their defaults,
and their documentation strings as a way to automatically build the site
documentation and keep it in sync.
> Log errors for unrecognized config options
> ------------------------------------------
>
> Key: KAFKA-181
> URL: https://issues.apache.org/jira/browse/KAFKA-181
> Project: Kafka
> Issue Type: Improvement
> Components: core
> Reporter: Joel Koshy
> Fix For: 0.8
>
>
> Currently, unrecognized config options are silently ignored. Notably, if a
> config has a typo or if a deprecated config is used, then there is no warning
> issued and defaults are assumed. One can argue that the broker or a consumer
> or a producer with an unrecognized config option should not even be allowed
> to start up especially if defaults are silently assumed, but it would be good
> to at least log an error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
