-
Notifications
You must be signed in to change notification settings - Fork 205
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
Allow sharing of Redis database #257
Comments
torfsen
added a commit
to torfsen/ckanext-harvest
that referenced
this issue
Jul 20, 2016
Previously purging the queue on the Redis backend would clear the whole database, making it hard to share the same database with other parts of CKAN. With this commit, only the keys that belong to ckanext-harvest and the current CKAN instance are purged.
This was referenced Jul 20, 2016
torfsen
added a commit
to torfsen/ckanext-harvest
that referenced
this issue
Jul 20, 2016
Previously purging the queue on the Redis backend would clear the whole database, making it hard to share the same database with other parts of CKAN. With this commit, only the keys that belong to ckanext-harvest and the current CKAN instance are purged.
davidread
pushed a commit
that referenced
this issue
Jul 20, 2016
[#257] Purge only our own Redis data.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CKAN core is currently moving towards Redis as a hard dependency, for example for its new background job queue (ckan/ckan#3165). This means that CKAN and ckanext-harvest should be able to share a Redis database.
ckanext-harvest already prefixes its Redis keys appropriately, but Redis queue purging currently empties the whole database. This must be fixed so that only the ckanext-harvest keys of the current CKAN instance are removed. That can be done using Redis' support for LUA scripts, see for example the queue cleaning in RQ.
The text was updated successfully, but these errors were encountered: