[
https://issues.apache.org/jira/browse/FLINK-5781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16006199#comment-16006199
]
ASF GitHub Bot commented on FLINK-5781:
---------------------------------------
Github user dawidwys commented on the issue:
https://github.com/apache/flink/pull/3495
It works exactly as you describe. The role of `defaultGroup` in
`ConfigGroups` is setting a name of the defaultGroup. I agree using
`ConfigGroup` for the `defaultGroup` may be counter intuitive.
What do you think of sth like:
```
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
@Internal
public @interface ConfigGroups {
String defaultGroupName();
ConfigGroup[] additionalGroups() default {};
}
```
or would you prefer removing it completely and just using the name of the
enclosing class?
> Generation HTML from ConfigOption
> ---------------------------------
>
> Key: FLINK-5781
> URL: https://issues.apache.org/jira/browse/FLINK-5781
> Project: Flink
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Ufuk Celebi
> Assignee: Dawid Wysakowicz
>
> Use the ConfigOption instances to generate a HTML page that we can use to
> include in the docs configuration page.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
