[
https://issues.apache.org/jira/browse/FLINK-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905072#comment-16905072
]
Aljoscha Krettek commented on FLINK-13696:
------------------------------------------
If the choice is between making {{ClosureCleaner}} a {{@Public}} component and
using {{ClosureCleaner}} in the connectors or other libraries, then I would
rather not use {{ClosureCleaner}} in the public APIs in order to keep the API
surface cleaner. The closure cleaner was really meant as an internal tool and
shouldn't be made public, I think.
> Revisit & update Flink's public API annotations
> ------------------------------------------------
>
> Key: FLINK-13696
> URL: https://issues.apache.org/jira/browse/FLINK-13696
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Critical
>
> We should revisit and update Flink's public API. As indicated by FLINK-13586,
> Flink's user facing classes and interfaces are not properly annotated. I
> think we should revisit this topic and rethink which classes and interfaces
> are part of Flink's public surface area with which users interact.
> For example, we have the {{ClosureCleaner}} which is used by several
> connector implementations. Consequently, the {{ClosureCleaner}} should be
> part of Flink's public API so that any changes to this class will be spotted
> by the {{japicmp}} plugin.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
