Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-32983

Support setting env.java.opts.all & env.java.opts.cli configs via dynamic properties on the CLI side

    XMLWordPrintableJSON

Details

    Description

      Problem

      The following configs are supposed to be supported:

      env.java.opts.all
      		 (none) String Java options to start the JVM of all Flink processes with.
      env.java.opts.client
      		 (none) String Java options to start the JVM of the Flink Client with.

      However, the two configs only takes effect on the Client side when they are set in the flink-conf files. In other words, configs set via -D or-yD on the CLI will not take effect, which is counter-intuitive and makes configuration less flexible.

       

      Proposal

      Add logic to parse configs set via -D or-yD in config.sh and make them has a higher precedence over configs set in flink-conf.yaml for env.java.opts.all & env.java.opts.client.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Zhanghao Chen Zhanghao Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: