You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sam Meder (JIRA)" <ji...@apache.org> on 2013/08/02 17:57:49 UTC
[jira] [Updated] (KAFKA-997) Provide a strict verification mode
when reading configuration properties
[ https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Meder updated KAFKA-997:
----------------------------
Attachment: strict-verification.patch
Add strict verification property and use it in tests and similar situations where config is constrained. Also fixed a couple of problems with out of date config in tests.
> Provide a strict verification mode when reading configuration properties
> ------------------------------------------------------------------------
>
> Key: KAFKA-997
> URL: https://issues.apache.org/jira/browse/KAFKA-997
> Project: Kafka
> Issue Type: Improvement
> Components: config
> Affects Versions: 0.8
> Reporter: Sam Meder
> Priority: Minor
> Fix For: 0.8
>
> Attachments: strict-verification.patch
>
>
> This ticket is based on the discussion in KAFKA-943. It introduces a new property that makes the config system throw an exception when it encounters unrecognized properties. (instead of a simple warn-level log statement). This new property defaults to false.
> Hopefully this will result in fewer instance of out-of-date configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira