flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Hogan <c...@greghogan.com>
Subject [DISCUSS] @Public libraries
Date Tue, 22 Nov 2016 17:56:44 GMT
Hi all,

Should stable APIs in Flink's CEP, ML, and Gelly libraries be annotated
@Public or restricted to use of @PublicEvolving?

We would ensure that library APIs do not add restrictions to the core APIs.
Libraries could use @PublicEvolving or @Internal core APIs within @Public
or @PublicEvolving components as long as the functionality could be adapted
or rewritten as necessary. An example: CombineHint is @Internal. Gelly
could use CombineHint in a @Public method but could not accept CombineHint
as a parameter to a @Public method.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message