Versions Compared

Old Version 3

changes.mady.by.user Zhanghao Chen

Saved on

compared with

New Version Current

changes.mady.by.user Zhanghao Chen

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Page properties

Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".

Discussion threadhere (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)thread/cflonyrfd1ftmyrpztzj3ywckbq41jzg
Vote threadhere (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)/thread/5qlr0xl0oyc9dnvcjr0q39pcrzyx4ohb
JIRA

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyFLINK-33221

Release<Flink Version>1.19


Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

Simple manual tests will do.

Rejected Alternatives

Prepend Administrator JVM Options to User JVM Options by Platform

An alternative is to maintain administrator JVM options in the platform's own config store and prepend them to the Flink JVM options when submitting the job. However, this approach is unfavored for two reasons:

  1. More difficult for users to resolve uncompatible JVM options as the administrator JVM options cannot be overriden by users directly as a normal Flink option now.
  2. More difficult for platform administrators to maintain administrator JVM options, as extra config assembly and management mechanism is needed.