[
https://issues.apache.org/jira/browse/FLINK-30774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17740452#comment-17740452
]
Matthias Pohl commented on FLINK-30774:
---------------------------------------
Hi [~alokh] thanks for volunteering. There's a discussion about Flink 2.0 going
right now (see [corresponding wiki
page|https://cwiki.apache.org/confluence/display/FLINK/2.0+Release] and [the
mailing list
thread|https://lists.apache.org/thread/l3dkdypyrovd3txzodn07lgdwtwvhgk4]) which
might also include reorganizing the module structure of Flink in some way. You
might want to follow the discussion on the mailing list regarding this and
other similar contributions. Therefore, I suggest to wait with working on this
issue until the next steps are clarified.
> Introduce flink-utils module
> ----------------------------
>
> Key: FLINK-30774
> URL: https://issues.apache.org/jira/browse/FLINK-30774
> Project: Flink
> Issue Type: Improvement
> Components: Build System
> Affects Versions: 1.17.0
> Reporter: Matthias Pohl
> Priority: Major
> Labels: starter
>
> Currently, utility methods generic utility classes like {{Preconditions}} or
> {{AbstractAutoCloseableRegistry}} are collected in {{flink-core}}. The flaw
> of this approach is that we cannot use those classes in modules like
> {{fink-migration-test-utils}}, {{flink-test-utils-junit}},
> {{flink-metrics-core}} or {{flink-annotations}}.
> We might want to have a generic {{flink-utils}} analogously to
> {{flink-test-utils}} that collects Flink-independent utility functionality
> that can be access by any module {{flink-core}} is depending on to make this
> utility functionality available in any Flink-related module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)