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.

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

Add support for SPUBLISH #2757 #2800

Closed
wants to merge 1 commit into from

Conversation

manish-manghwani
Copy link

implementation for #2757

Due to its similarity with PUBLISH and PUBSUB SHARDCHANNELS command, implementation is done in same way.
Test cases are not covered, can anyone give guidance on what all test cases should be covered for SPUBLISH Command.

Make sure that:

  • You have read the contribution guidelines.
  • You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.

Copy link
Collaborator

@tishun tishun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please also add the new command in the templates under src/main/templates/io/lettuce/core/api/BaseRedisCommands.java ?

This would allow us (if we decide to use the apigenerator in the /test tree) to generate the same signature.

Unfortunately we seem to be a bit shy on unit tests for the pub sub commands.
I would appreciate if you can add some, at least for the code you added.
Not mandatory considering we do not have any.

We would also want to add integration tests for this, especially if we want to verify the cluster specifics, in the following places:

  • RedisClusterPubSubConnectionIntegrationTest
  • PubSubCommantTest
  • PubSubReactiveTest

However testing would be mostly impossible without the SSUBSCRIBE command implemented, as it would be hard to verify anything was published. I suggest leaving method stubs (with some or no implementation, but explaining what we need to test) with annotation @EnabledOnCommand("SSUBSCRIBE"), see #2776

@mp911de
Copy link
Collaborator

mp911de commented Apr 2, 2024

Care to rebase your pull request, given the conflicting changes?

@atakavci
Copy link
Collaborator

atakavci commented Apr 3, 2024

hey @manish-manghwani ,

i got backgrounds of this while i was working on #2813 .
do you mind if i take over this one ?

@manish-manghwani
Copy link
Author

manish-manghwani commented Apr 3, 2024

hey @manish-manghwani ,

i got backgrounds of this while i was working on #2813 . do you mind if i take over this one ?

hey @atakavci, sure please take over.

Do I need to close this PR?

@atakavci
Copy link
Collaborator

atakavci commented Apr 4, 2024

thanks, please do close this one.
you can follow #2757 if you want to see the changes

@tishun tishun added the type: feature A new feature label Apr 12, 2024
@tishun tishun modified the milestones: 7.0.0.RELEASE, 6.4.0.RELEASE Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature A new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants