We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since eLevelDB expiry was introduced to 2.2, theres no specific documentation under Riak on how to configure this setting. http://docs.basho.com/riak/kv/2.2.0/configuring/backend/
The only related configuration information can be found in the Riak TS documentation. http://docs.basho.com/riak/ts/1.4.0/using/global-object-expiration/
This is related to ticket #14235
The text was updated successfully, but these errors were encountered:
Joe mentioned this during out meeting today: http://docs.basho.com/riak/kv/2.2.0/configuring/global-object-expiration/
I would still suggest that this link should be included in http://docs.basho.com/riak/kv/2.2.0/configuring/reference/#storage-backend and http://docs.basho.com/riak/kv/2.2.0/setup/planning/backend/leveldb/#configuring-eleveldb
Using the search box also does not list the KV page as one possible link.
Sorry, something went wrong.
No branches or pull requests
Since eLevelDB expiry was introduced to 2.2, theres no specific documentation under Riak on how to configure this setting. http://docs.basho.com/riak/kv/2.2.0/configuring/backend/
The only related configuration information can be found in the Riak TS documentation. http://docs.basho.com/riak/ts/1.4.0/using/global-object-expiration/
This is related to ticket #14235
The text was updated successfully, but these errors were encountered: