flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-8192) Properly annotate APIs of all Flink connectors with @Public / @PublicEvolving / @Internal
Date Fri, 08 Dec 2017 13:42:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-8192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16283523#comment-16283523

ASF GitHub Bot commented on FLINK-8192:

Github user greghogan commented on the issue:

    Changes to the public API require a [FLIP](https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals).

> 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
>             Fix For: 1.5.0
> 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

View raw message