[
https://issues.apache.org/jira/browse/KAFKA-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010310#comment-14010310
]
Sam Meder commented on KAFKA-997:
---------------------------------
Looked at this a bit more a while ago and am just going to close the issue. The
config system currently needs to be extensible (for e.g. metrics system
properties) so making strict verification work without clear namespacing and
extension rules is impossible. We're instead taking the approach of creating
internal constants for all the Kafka properties, so we can manage and detect
change that way.
> 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
> Reporter: Sam Meder
> Assignee: Sam Meder
> Priority: Minor
> Fix For: 0.8.2
>
> Attachments: strict-verification-2.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 was sent by Atlassian JIRA
(v6.2#6252)
