Skip to content

Conversation

@intsmaze
Copy link
Contributor

Stateback provides api implementations of FsStateBackend and MemoryStateBackend by default. Add the RocksDBStateBackend dependency if you want to use the RocksDBStateBackend api.

What is the purpose of the change

Stateback provides api implementations of FsStateBackend and MemoryStateBackend by default. Add the RocksDBStateBackend dependency if you want to use the RocksDBStateBackend api.

Brief change log

  • Add the RocksDBStateBackend dependency

Verifying this change

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): ( no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)

Stateback provides api implementations of FsStateBackend and MemoryStateBackend by default. Add the RocksDBStateBackend dependency if you want to use the RocksDBStateBackend api.
@asfgit asfgit closed this in f305b64 Jan 14, 2019
@intsmaze intsmaze changed the title Update state_backends.md Update state_backends.md about add the RocksDBStateBackend dependency Jan 14, 2019
tisonkun pushed a commit to tisonkun/flink that referenced this pull request Jan 17, 2019
…ends.md

In order to use the RocksDBStateBackend, the user has to add the flink-statebackend-rocksdb
dependency to his project. This commit adds this information to the state_backends.md.

This closes apache#7480.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant