[
https://issues.apache.org/jira/browse/FLINK-13696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13696:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
auto-deprioritized-minor (was: auto-deprioritized-critical
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-deprioritized-minor
>
> 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
(v8.20.1#820001)
