You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/05/25 16:22:08 UTC

[jira] [Updated] (FLINK-8192) Properly annotate APIs of all Flink connectors with @Public / @PublicEvolving / @Internal

     [ https://issues.apache.org/jira/browse/FLINK-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Till Rohrmann updated FLINK-8192:
---------------------------------
    Fix Version/s:     (was: 1.5.0)
                   1.5.1

> Properly annotate APIs of all Flink connectors with @Public / @PublicEvolving / @Internal
> -----------------------------------------------------------------------------------------
>
>                 Key: FLINK-8192
>                 URL: https://issues.apache.org/jira/browse/FLINK-8192
>             Project: Flink
>          Issue Type: Improvement
>          Components: Streaming Connectors
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Major
>             Fix For: 1.5.1
>
>
> Currently, the APIs of the Flink connectors have absolutely no annotations on whether their usage is {{Public}} / {{PublicEvolving}} / or {{Internal}}.
> We have, for example, instances in the past where a user was mistakenly using an abstract internal base class in the Elasticsearch connector.
> This JIRA tracks the coverage of API usage annotation for all Flink shipped connectors. Ideally, a separate subtask should be created for each individual connector.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)