Identify spring-data-redis using underlying drivers (jedis or lettuce) #3268
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change introduces the ability to identify spring-data-redis clients on the server side using the underlying drivers (jedis and lettuce) and the CLIENT SETINFO command.
As part of the change, the following capabilities are made available:
This feature establishes the foundation for future integrations that require identification of client libraries using spring-data-redis.
The changes are available as part of the following classes:
This feature is available starting from Redis OSS version 7.2.x and later