[
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 stale-major (was:
auto-deprioritized-critical)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-deprioritized-critical, stale-major
>
> 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.3.4#803005)
