[ https://issues.apache.org/jira/browse/FLINK-32250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-32250: ----------------------------------- Labels: pull-request-available (was: ) > Revert the Field name of BUFFER_TIMEOUT to improve compatibility > ---------------------------------------------------------------- > > Key: FLINK-32250 > URL: https://issues.apache.org/jira/browse/FLINK-32250 > Project: Flink > Issue Type: Bug > Components: API / DataStream > Affects Versions: 1.18.0 > Reporter: Rui Fan > Assignee: Rui Fan > Priority: Major > Labels: pull-request-available > Fix For: 1.18.0 > > > FLINK-32023 changed the `ExecutionOptions.BUFFER_TIMEOUT` to > `ExecutionOptions.BUFFER_TIMEOUT_INTERVAL`, the filed name should be reverted. > Because the `ExecutionOptions` is a public evolving API, some flink users are > using the `ExecutionOptions.BUFFER_TIMEOUT` in their code. If we update it, > the code cannot upgrade to 1.18 directly. > > BTW, the option name is changed from `execution.buffer-timeout` to > `execution.buffer-timeout.interval`. However, we marked the > `execution.buffer-timeout` as `DeprecatedKeys`. So 1.18 is compatible with > the old option name. > -- This message was sent by Atlassian Jira (v8.20.10#820010)