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.

Sign up for GitHub

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

Jump to bottom

Why does setTriggerState/unsetTriggerState get new connection? #4

Open
adrianriley opened this issue Apr 8, 2015 · 1 comment
Open

Why does setTriggerState/unsetTriggerState get new connection? #4

adrianriley opened this issue Apr 8, 2015 · 1 comment

Comments

@adrianriley
Copy link

I'm interested to know why these methods always get a new Jedis instance from the pool, even when the calling method already has an instance. Is there a particular reason not to use the same one?
@abhishek-goyal
Copy link

Hi @adrianriley, @kehati : Did we ever get an answer to this one?
If separate connection is not needed, I can make a small fix for this and raise a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adrianriley @abhishek-goyal