[
https://issues.apache.org/jira/browse/KAFKA-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979754#comment-14979754
]
ASF GitHub Bot commented on KAFKA-2702:
---------------------------------------
GitHub user granthenke opened a pull request:
https://github.com/apache/kafka/pull/379
KAFKA-2702: ConfigDef toHtmlTable() sorts in a way that is a bit conf…
…using
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/granthenke/kafka config-html
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/379.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 #379
----
commit 257655b3b5a6f0a374332c6d403bbcc117844117
Author: Grant Henke <granthe...@gmail.com>
Date: 2015-10-29T03:49:24Z
KAFKA-2702: ConfigDef toHtmlTable() sorts in a way that is a bit confusing
----
> ConfigDef toHtmlTable() sorts in a way that is a bit confusing
> --------------------------------------------------------------
>
> Key: KAFKA-2702
> URL: https://issues.apache.org/jira/browse/KAFKA-2702
> Project: Kafka
> Issue Type: Bug
> Reporter: Gwen Shapira
> Assignee: Grant Henke
>
> Because we put everything without default first (without prioritizing),
> critical parameters get placed below low priority ones when they both have
> no defaults. Some parameters are without default and optional (SASL server in
> ConsumerConfig for instance).
> Try printing ConsumerConfig parameters and see the mandatory group.id show up
> as #15.
> I suggest sorting the no-default parameters by priority as well, or perhaps
> adding a "REQUIRED" category that gets printed first no matter what.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
