GitHub user benstopford opened a pull request:

    https://github.com/apache/kafka/pull/1864

    Kafka-4177: Remove ThrottledReplicationRateLimit from Server Config 

    This small PR pulls ThrottledReplicationRateLimit out of KafkaConfig and 
puts it in a class that defines Dynamic Configs. Client configs are also placed 
in this class and validation added. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/benstopford/kafka KAFKA-4177

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1864.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1864
    
----
commit 63fbfe2f464b92aba7513c90086feed5d3afca33
Author: Ben Stopford <benstopf...@gmail.com>
Date:   2016-09-16T14:26:01Z

    KAFKA-4177: Minor refactor to pull the dynamic broker property 
replication.quota.throttled.rate out of KafkaConfig and its own class 
collocated with the ConfigCommand/AdminUtils

commit 72ddadd42088127d2d4bdfb812079145e534bb1e
Author: Ben Stopford <benstopf...@gmail.com>
Date:   2016-09-16T14:43:26Z

    KAFKA-4177:  Refactored to include dynamic client configs also

commit d51be065112ed398b82c966a38ad8f2ef8fc0f04
Author: Ben Stopford <benstopf...@gmail.com>
Date:   2016-09-16T15:08:16Z

    KAFKA-4177:  Move to kafka.server package

commit 495c17c53a0c64e8ea539dad52508a20ca7b4c5c
Author: Ben Stopford <benstopf...@gmail.com>
Date:   2016-09-16T15:13:14Z

    KAFKA-4177:  Moved tests to its own class

commit 3a609d9f52c0be49c4b37055f3e73f6002b2e31d
Author: Ben Stopford <benstopf...@gmail.com>
Date:   2016-09-16T15:16:02Z

    KAFKA-4177:  Whitespace only

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to