[
https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161318#comment-14161318
]
Gwen Shapira commented on KAFKA-1667:
-------------------------------------
Looks like LogConfig has very few validations.
I think it makes sense to refactor it to use either ConfigDef (actually part of
the client code, but has really nice validators) or at least
ValidatedProperties instead of just Properties - and then we can add proper
validation for each config.
Any thoughts on whether ConfigDef can be used in the server, or if we should
keep on using ValidatedProperties?
> topic-level configuration not validated
> ----------------------------------------
>
> Key: KAFKA-1667
> URL: https://issues.apache.org/jira/browse/KAFKA-1667
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.1.1
> Reporter: Ryan Berdeen
> Labels: newbie
>
> I was able to set the configuration for a topic to these invalid values:
> {code}
> Topic:topic-config-test PartitionCount:1 ReplicationFactor:2
> Configs:min.cleanable.dirty.ratio=-30.2,segment.bytes=-1,retention.ms=-12,cleanup.policy=lol
> {code}
> It seems that the values are saved as long as they are the correct type, but
> are not validated like the corresponding broker-level properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
