Skip to content
New issue

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

eLevelDB Backend Expiry Configuration [JIRA: DOC-730] #2322

Open
pogzie opened this issue Dec 5, 2016 · 1 comment
Open

eLevelDB Backend Expiry Configuration [JIRA: DOC-730] #2322

pogzie opened this issue Dec 5, 2016 · 1 comment

Comments

@pogzie
Copy link
Contributor

pogzie commented Dec 5, 2016

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

@Basho-JIRA Basho-JIRA changed the title eLevelDB Backend Expiry Configuration eLevelDB Backend Expiry Configuration [JIRA: DOC-730] Dec 5, 2016
@pogzie
Copy link
Contributor Author

pogzie commented Dec 6, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants