Document the state by adding a label to the FLIP page with one of "discussion", "accepted", "released", "rejected".

Discussion threadhere (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)
Vote threadhere (<- link to https://lists.apache.org/list.html?dev@flink.apache.org)
JIRAhere (<- link to https://issues.apache.org/jira/browse/FLINK-XXXX)
Release2.0

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Properly reflect the state of the rocksdb statebackend by moving it out of the "contrib" package.

Public Interfaces

  • EmbeddedRocksDBStateBackend

  • EmbeddedRocksDBStateBackendFactory

Proposed Changes

Move all classes in the state-backend-rocksdb module under the classes to o.a.f.state.rocksdb package.

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?
  • Programmatic usages of the RocksDBStatebackend will need to be updated.
  • If we are changing behavior how will we phase out the older behavior?
  • Deprecate the old public interfaces. We could consider adding 2 classes in 1.x that life in the intended package, merely extending the deprecated classes.