[
https://issues.apache.org/jira/browse/FLINK-33965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801998#comment-17801998
]
Rui Fan commented on FLINK-33965:
---------------------------------
Merged to main(1.8.0) via : fa938439ad8a7601462a3be268077aa4078881bc and
3cae5907d3a5c610a1aa8e5d41095ddbcba676ef
> Refactor the configuration for autoscaler standalone
> ----------------------------------------------------
>
> Key: FLINK-33965
> URL: https://issues.apache.org/jira/browse/FLINK-33965
> Project: Flink
> Issue Type: Sub-task
> Reporter: Rui Fan
> Assignee: Rui Fan
> Priority: Major
> Labels: pull-request-available
>
> Currently, all configurations of autoscaler standalone are maintained in
> string key.
> When autoscaler standalone has a little options, it's easy to maintain.
> However, I found it's hard to maintain when we add more options.
> During I developing the JDBC autoscaler state store and control loop supports
> multiple thread. It will introduce more options.
> h2. Solution:
> Introducing the AutoscalerStandaloneOptions to manage all options of
> autoscaler standalone. And output the doc for it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
