Hi! The beta status refers exactly to API stability and test coverage.
Full status APIs, like the batch API, are very stable. For example, we have not made any breaking changes in the last two releases (except for rare corner case flags). The test coverage is also pretty good. Beta APIs (like streaming, or ML) may undergo some breaking changes. The streaming API is currently finalized and will most likely go out of beta (to full status) in the next release in some weeks. Then the API will not be broken again as well. Feature completeness is a bit of a vague question. I think all core features are implemented (features you need for production use), in that sense it is feature complete. Still, every release adds new features to almost every API, be that convenience features or new constructs for efficiency, useful semantics, ... Concerning production readiness, people run this in production (both batch and streaming). Greetings, Stephan On Thu, Aug 20, 2015 at 8:16 AM, ankurcha <an...@malloc64.com> wrote: > Hi, > > This is a more of a semantics / scope question. What does it mean by the > "beta" status? > > Main questions are around: > > * API stability - How stable is the API? > * Regression / testing coverage? > * Feature completeness? > * Production readiness? > > Also, a pointer to the relevant roadmaps and/or planning documents would be > very helpful. > > -- Ankur Chauhan > > > > -- > View this message in context: > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DataStream-API-What-does-Beta-mean-tp7582.html > Sent from the Apache Flink Mailing List archive. mailing list archive at > Nabble.com. >
