[
https://issues.apache.org/jira/browse/KAFKA-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198212#comment-14198212
]
Dmytro Kostiuchenko commented on KAFKA-1667:
--------------------------------------------
Hi. I'm willing to work on this.
Currently I have few questions:
# What should be of a higher priority: keeping same interface for LogConfig or
making code consistent with other configs based on ConfigDef? In the latter
case changes would also impact AdminUtils, TopicCommand and perhaps some other
classes.
# Are there any guidelines to assigning priorities?
# Is there some place to check for valid ranges for properties? It is always
possible to induce them from the code, but would be easier, of course, to have
some reference doc.
Thanks
> 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)
