[
https://issues.apache.org/jira/browse/FLINK-39130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18061000#comment-18061000
]
Rui Fan edited comment on FLINK-39130 at 2/26/26 9:06 AM:
----------------------------------------------------------
Merged to
master 2.3.0 via: 9964ab4bd1b8334dec9388e1e4dac68c94488691
2.2.1 via: a68f4d4125d1d1055bd84186fa924d540852c33e
2.1.2 via: f5effd704c134a6487d62930d6e9e334e2811f9f
was (Author: fanrui):
Merged to master to 2.3.0 via: 9964ab4bd1b8334dec9388e1e4dac68c94488691
> Allow native types to be used for MetricConfig
> ----------------------------------------------
>
> Key: FLINK-39130
> URL: https://issues.apache.org/jira/browse/FLINK-39130
> Project: Flink
> Issue Type: Bug
> Reporter: Aleksandr Iushmanov
> Assignee: Aleksandr Iushmanov
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.1.2, 2.3.0, 2.2.1
>
>
> In Flink-2.0+ Yaml parsing allows to place `Number` in the config, but
> `MetricConfig.java` implementation only parses strings. Allowing parsing
> native types protects users from the need to use "strings" for non-string
> MetricConfigs
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
