-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ISSUE-1024 keyPrefix option support Redis Cluster #1041
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 7 days if no further activity occurs, but feel free to re-open a closed issue if needed. |
@luin Could the bugfix be merged into the trunk? |
We're looking for this to be merged as well |
What about this bug? We hit this issue today. This is a crazy simple bugfix and it is waiting for a merge for over 5 months already. |
Sorry for the late response. It was indeed an oversight but the fix is somehow a breaking change so I think we should ship this fix in the next major release. For now, we may add a usage notice to README.md to save people's time. Thanks for the contribution @cobolbaby ! |
To be honest I wouldn't consider it as breaking change but bugfix. For this moment I had to add it to top-level options and it works with Cluster but this is hopefully not long term solution... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lookgs good
when is this shipping ? |
why exactly is this a breaking change? |
This should be a bugfix.. or please update the documents :'( when is the next major release? any updates? |
Hey @cobolbaby 👋 |
#1024