[jira] [Updated] (FLINK-15458) Allow specific options to have non-unique key

["Chesnay Schepler (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler updated FLINK-15458:
-------------------------------------
    Summary: Allow specific options to have non-unique key  (was: Add whitelist for ambiguous config options)

> Allow specific options to have non-unique key
> ---------------------------------------------
>
>                 Key: FLINK-15458
>                 URL: https://issues.apache.org/jira/browse/FLINK-15458
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation, Runtime / Configuration
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The {{ConfigOptionsDocsCompletenessITCase}} verifies that all existing and documented options are well-defined; as in that for any key there is exactly 1 default and description present, globally.
>  
> There is one use-case however where this check is too strict: reporters. These only work with key suffixes (like "port") and hence are failing this check. As a result we don't use the generator mechanism for reporters, which is unfortunate.
>  
> I propose to slightly extend this test so that this check is not performed for specific keys.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)