[jira] [Updated] (FLINK-35359) General Improvement to Configuration for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-35359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xintong Song updated FLINK-35359: - Release Note: The following configurations have been updated to the Duration type in a backward-compatible manner: - `client.heartbeat.interval` - `client.heartbeat.timeout` - `cluster.registration.error-delay` - `cluster.registration.initial-timeout` - `cluster.registration.max-timeout` - `cluster.registration.refused-registration-delay` - `cluster.services.shutdown-timeout` - `heartbeat.interval` - `heartbeat.timeout` - `high-availability.zookeeper.client.connection-timeout` - `high-availability.zookeeper.client.retry-wait` - `high-availability.zookeeper.client.session-timeout` - `historyserver.archive.fs.refresh-interval` - `historyserver.web.refresh-interval` - `metrics.fetcher.update-interval` - `metrics.latency.interval` - `metrics.reporter.influxdb.connectTimeout` - `metrics.reporter.influxdb.writeTimeout` - `metrics.system-resource-probing-interval` - `pekko.startup-timeout` - `pekko.tcp.timeout` - `resourcemanager.job.timeout` - `resourcemanager.standalone.start-up-time` - `resourcemanager.taskmanager-timeout` - `rest.await-leader-timeout` - `rest.connection-timeout` - `rest.idleness-timeout` - `rest.retry.delay` - `slot.idle.timeout` - `slot.request.timeout` - `task.cancellation.interval` - `task.cancellation.timeout` - `task.cancellation.timers.timeout` - `taskmanager.debug.memory.log-interval` - `web.refresh-interval` - `web.timeout` - `yarn.heartbeat.container-request-interval` The following configurations have been updated to the Enum type in a backward-compatible manner: - `taskmanager.network.compression.codec` - `table.optimizer.agg-phase-strategy` The following configurations have been updated to the Int type in a backward-compatible manner: - `yarn.application-attempts` was: - The following configurations have been updated to the Duration type in a backward-compatible manner: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval`. - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. > General Improvement to Configuration for Flink 2.0 > -- > > Key: FLINK-35359 > URL: https://issues.apache.org/jira/browse/FLINK-35359 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration >Reporter: Xuannan Su >Assignee: Xuannan Su >Priority: Major > Labels: pull-request-available > > As Flink moves toward version 2.0, we want to provide users with a better > experience with the existing configuration. In this FLIP, we outline several > general improvements to the current configuration: > * Ensure all the ConfigOptions are properly annotated > * Ensure all user-facing configurations are included in the documentation > generation process > * Make the existing ConfigOptions use the proper type > * Mark all internally used ConfigOptions with the @Internal annotation > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-442%3A+General+Improvement+to+Configuration+for+Flink+2.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35359) General Improvement to Configuration for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-35359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuannan Su updated FLINK-35359: --- Release Note: - The following configurations have been updated to the Duration type in a backward-compatible manner: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval`. - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. was: - The following configurations have been updated to the Duration type in a backward-compatible manner: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval` - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. > General Improvement to Configuration for Flink 2.0 > -- > > Key: FLINK-35359 > URL: https://issues.apache.org/jira/browse/FLINK-35359 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration >Reporter: Xuannan Su >Assignee: Xuannan Su >Priority: Major > Labels: pull-request-available > > As Flink moves toward version 2.0, we want to provide users with a better > experience with the existing configuration. In this FLIP, we outline several > general improvements to the current configuration: > * Ensure all the ConfigOptions are properly annotated > * Ensure all user-facing configurations are included in the documentation > generation process > * Make the existing ConfigOptions use the proper type > * Mark all internally used ConfigOptions with the @Internal annotation > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-442%3A+General+Improvement+to+Configuration+for+Flink+2.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35359) General Improvement to Configuration for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-35359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuannan Su updated FLINK-35359: --- Release Note: - The following configurations have been updated to the Duration type in a backward-compatible manner: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval` - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. was: - The following configurations have been updated to the Duration type in a backward-compatible manner:: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval`, - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. > General Improvement to Configuration for Flink 2.0 > -- > > Key: FLINK-35359 > URL: https://issues.apache.org/jira/browse/FLINK-35359 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration >Reporter: Xuannan Su >Assignee: Xuannan Su >Priority: Major > Labels: pull-request-available > > As Flink moves toward version 2.0, we want to provide users with a better > experience with the existing configuration. In this FLIP, we outline several > general improvements to the current configuration: > * Ensure all the ConfigOptions are properly annotated > * Ensure all user-facing configurations are included in the documentation > generation process > * Make the existing ConfigOptions use the proper type > * Mark all internally used ConfigOptions with the @Internal annotation > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-442%3A+General+Improvement+to+Configuration+for+Flink+2.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35359) General Improvement to Configuration for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-35359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuannan Su updated FLINK-35359: --- Release Note: - The following configurations have been updated to the Duration type in a backward-compatible manner:: `client.heartbeat.interval`, `client.heartbeat.timeout`, `cluster.registration.error-delay`, `cluster.registration.initial-timeout`, `cluster.registration.max-timeout`, `cluster.registration.refused-registration-delay`, `cluster.services.shutdown-timeout`, `heartbeat.interval`, `heartbeat.timeout`, `high-availability.zookeeper.client.connection-timeout`, `high-availability.zookeeper.client.retry-wait`, `high-availability.zookeeper.client.session-timeout`, `historyserver.archive.fs.refresh-interval`, `historyserver.web.refresh-interval`, `metrics.fetcher.update-interval`, `metrics.latency.interval`, `metrics.reporter.influxdb.connectTimeout`, `metrics.reporter.influxdb.writeTimeout`, `metrics.system-resource-probing-interval`, `pekko.startup-timeout`, `pekko.tcp.timeout`, `resourcemanager.job.timeout`, `resourcemanager.standalone.start-up-time`, `resourcemanager.taskmanager-timeout`, `rest.await-leader-timeout`, `rest.connection-timeout`, `rest.idleness-timeout`, `rest.retry.delay`, `slot.idle.timeout`, `slot.request.timeout`, `task.cancellation.interval`, `task.cancellation.timeout`, `task.cancellation.timers.timeout`, `taskmanager.debug.memory.log-interval`, `web.refresh-interval`, `web.timeout`, `yarn.heartbeat.container-request-interval`, - The `taskmanager.network.compression.codec` and `table.optimizer.agg-phase-strategy` configurations have been updated to the Enum type in a backward-compatible manner. - The `yarn.application-attempts` configuration has been updated to the Int type in a backward-compatible manner. > General Improvement to Configuration for Flink 2.0 > -- > > Key: FLINK-35359 > URL: https://issues.apache.org/jira/browse/FLINK-35359 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration >Reporter: Xuannan Su >Assignee: Xuannan Su >Priority: Major > Labels: pull-request-available > > As Flink moves toward version 2.0, we want to provide users with a better > experience with the existing configuration. In this FLIP, we outline several > general improvements to the current configuration: > * Ensure all the ConfigOptions are properly annotated > * Ensure all user-facing configurations are included in the documentation > generation process > * Make the existing ConfigOptions use the proper type > * Mark all internally used ConfigOptions with the @Internal annotation > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-442%3A+General+Improvement+to+Configuration+for+Flink+2.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-35359) General Improvement to Configuration for Flink 2.0
[ https://issues.apache.org/jira/browse/FLINK-35359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-35359: --- Labels: pull-request-available (was: ) > General Improvement to Configuration for Flink 2.0 > -- > > Key: FLINK-35359 > URL: https://issues.apache.org/jira/browse/FLINK-35359 > Project: Flink > Issue Type: Improvement > Components: Runtime / Configuration >Reporter: Xuannan Su >Priority: Major > Labels: pull-request-available > > As Flink moves toward version 2.0, we want to provide users with a better > experience with the existing configuration. In this FLIP, we outline several > general improvements to the current configuration: > * Ensure all the ConfigOptions are properly annotated > * Ensure all user-facing configurations are included in the documentation > generation process > * Make the existing ConfigOptions use the proper type > * Mark all internally used ConfigOptions with the @Internal annotation > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-442%3A+General+Improvement+to+Configuration+for+Flink+2.0 > -- This message was sent by Atlassian Jira (v8.20.10#820010)