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?
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
