-
Notifications
You must be signed in to change notification settings - Fork 22
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
FEATURE: Support lettuce 6.5.0 #62
Comments
Would be nice to have the PR |
Actually I think that we need to support the existing API and this is more of a regression in Lettuce 6.5.0 I will log another issue to research if we can add the missing constructor in 6.5.1 |
Lettuce 6.5.1 now produces the following:
|
My bad, will try to go over all the changes this time, tracked in redis/lettuce#3070 |
Thank you sir. If/when you have a SNAPSHOT ready for lettuce, I am happy to test with the changeset and report live feedback before the final release. |
Folks, redis/lettuce#3070 returns the missing public APIs, but there are quite a few things that are still incompatible in regards to the existing lettucemod JSON APIs and the newly introduced JSON APIs in Lettuce. I am afraid - from the perspective of the Lettuce driver - we could not shape the API surface so it does not break pre-existing APIs of consuming frameworks that extend it. Please check out the latest changes and let me know what you think. |
Using Lettuce 6.5.2 now produces:
|
Yes, I should have elaborated more on what I meant. This is expected as both lettucemod and the underlying driver Lettuce now support RedisJSON, as part of redis/lettuce#2933. As the signature of the Redis commands is the same we have collisions of namespaces - in this case both lettucemod and Lettuce provide the same method I would leave it to the maintainers to comment what they think the best approach would be to handle this situation. IMHO, unless lettucemod provides anything on top of what Lettuce provides in this case, we should deprecate these APIs where possible and start using the new ones provided by Lettuce. |
FWIW, I second this approach. Using stock Lettuce functionality in scenarios where the functionality is identical seems best. |
Since Lettuce now supports JSON I have removed the corresponding API from Lettucemod (released in 4.2.0). This allows upgrading to Lettuce 6.5.x and resolves this issue. |
Lettucemod 4.2.1 at the moment is built against Lettuce 6.4. Supporting Lettuce 6.5 will require some work given some APIs have changed. At the moment, using Lettuce 6.5 presents the following error:
The constructor in question has changed its signature to the following:
If you'd like to see a pull request, please let me know.
The text was updated successfully, but these errors were encountered: