Skip to content
This repository has been archived by the owner on May 30, 2024. It is now read-only.

Allow existing redis client to be passed into redis_feature_store #131

Conversation

rmanalan
Copy link
Contributor

@rmanalan rmanalan commented Nov 28, 2018

Currently, the redis_feature_store instantiates and manages a new
connection to redis. Many services that use redis already may opt to
just reuse an existing connection using their desired client. This
configuration allows for use of ioredis.

Related to #122

Currently, the redis_feature_store instantiates and manages a new
connection to redis. Many services that use redis already may opt to
just reuse an existing connection using their desired client. This
configuration allows for use of ioredis.
@rmanalan
Copy link
Contributor Author

@eli-darkly I went with the easy approach and just allowed an existing client to be passed in. I didn't end up implementing the locking mechanism, but something you guys should think of for all your clients... especially your redis clients. I was originally looking to add redlock to this, but the changes seemed out of scope for this particular PR.

eli-darkly added a commit that referenced this pull request Apr 2, 2019
@eli-darkly
Copy link
Contributor

Sorry this fell through the cracks. It looks fine, but I'm holding off on merging it until after a patch release that's currently in the works, since this would be a minor version bump.

@eli-darkly eli-darkly merged commit 5d40243 into launchdarkly:master Oct 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants