[jira] [Commented] (FLINK-30183) We should add a proper error message in case the deprecated reflection-based instantiation of a reporter is triggered

["Chesnay Schepler (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-30183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638204#comment-17638204 ] 

Chesnay Schepler commented on FLINK-30183:
------------------------------------------

We already have a log message for that.

https://github.com/apache/flink/blob/af6eff873a53bbdc85a2b1018140754e65758e3e/flink-runtime/src/main/java/org/apache/flink/runtime/metrics/ReporterSetup.java#L380

> We should add a proper error message in case the deprecated reflection-based instantiation of a reporter is triggered
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-30183
>                 URL: https://issues.apache.org/jira/browse/FLINK-30183
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>    Affects Versions: 1.16.0
>            Reporter: Matthias Pohl
>            Priority: Major
>              Labels: starter
>
> A [user reported an issue|https://lists.apache.org/thread/yjv0hof5qqnzq22xcjf3y2v61j48gqh4] with the {{PrometheusReporter}} instantiation. The {{NoSuchMethodException}} is caused by the {{PromethusReporter}} not having a default constructor implemented. Instead, the user should switch to the factory class approach.
> We might want to log a warning if the reflection-based approach still works but wrap the {{NoSuchMethodException}} into a {{IllegalConfigurationException}} with a proper error message pointing to the factory-based approach



--
This message was sent by Atlassian Jira
(v8.20.10#820010)