[
https://issues.apache.org/jira/browse/FLINK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142454#comment-15142454
]
ASF GitHub Bot commented on FLINK-3367:
---------------------------------------
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1606#issuecomment-182778295
The motivation for this was to to make those Internal which can be added
via the ExecutionEnvironment. Sources that offer configuration parameters which
are not accessible via the ExecutionEnvironment are PublicEvolving.
Does that make sense or should we make all PublicEvolving?
> Annotate all user-facing API classes with @Public or @PublicEvolving
> --------------------------------------------------------------------
>
> Key: FLINK-3367
> URL: https://issues.apache.org/jira/browse/FLINK-3367
> Project: Flink
> Issue Type: Task
> Affects Versions: 1.0.0
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Fix For: 1.0.0
>
>
> At the moment, only stable public classes are annotated with @Public. It is
> not possible to identify whether a non-annotated class is supposed to be
> API-facing or not.
> This issue proposes to annotate all API classes either with @Public or
> @PublicEvolving. Classes which are not annotated belong to Flink's internals.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
