[jira] [Commented] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

2023-02-01 Thread Chesnay Schepler (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683034#comment-17683034 ] Chesnay Schepler commented on FLINK-30862: -- ??The question is why we didn't clean up and remove

[jira] [Commented] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

2023-02-01 Thread Dawid Wysakowicz (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683005#comment-17683005 ] Dawid Wysakowicz commented on FLINK-30862: -- An alternative, that've just popped in my mind is

[jira] [Commented] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

2023-02-01 Thread Dawid Wysakowicz (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683001#comment-17683001 ] Dawid Wysakowicz commented on FLINK-30862: -- I second [~chesnay]. I don't think we should

[jira] [Commented] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

2023-02-01 Thread Jing Ge (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682975#comment-17682975 ] Jing Ge commented on FLINK-30862: - Fair enough. Thanks for the info. The question is why we didn't clean

[jira] [Commented] (FLINK-30862) Config doc generation should keep @deprecated ConfigOption

2023-02-01 Thread Chesnay Schepler (Jira)
[ https://issues.apache.org/jira/browse/FLINK-30862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682972#comment-17682972 ] Chesnay Schepler commented on FLINK-30862: -- I disagree. There are 2 possible scenarios: a) an