diff --git a/CODE_OF_CONDUCT.adoc b/CODE_OF_CONDUCT.adoc
index f64fb1b7a5..33ae7bc9f1 100644
--- a/CODE_OF_CONDUCT.adoc
+++ b/CODE_OF_CONDUCT.adoc
@@ -24,4 +24,4 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be repor
All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
-This Code of Conduct is adapted from the http://contributor-covenant.org[Contributor Covenant], version 1.3.0, available at http://contributor-covenant.org/version/1/3/0/[contributor-covenant.org/version/1/3/0/].
\ No newline at end of file
+This Code of Conduct is adapted from the https://contributor-covenant.org[Contributor Covenant], version 1.3.0, available at https://contributor-covenant.org/version/1/3/0/[contributor-covenant.org/version/1/3/0/].
\ No newline at end of file
diff --git a/README.md b/README.md
index 6a33445c03..b81013cc4c 100644
--- a/README.md
+++ b/README.md
@@ -1,15 +1,15 @@
-[](http://projects.spring.io/spring-data-redis/#quick-start)
-[](http://projects.spring.io/spring-data-redis/#quick-start)
+[](https://projects.spring.io/spring-data-redis/#quick-start)
+[](https://projects.spring.io/spring-data-redis/#quick-start)
Spring Data Redis
=======================
-The primary goal of the [Spring Data](http://projects.spring.io/spring-data/) project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services.
-This modules provides integration with the [Redis](http://redis.io/) store.
+The primary goal of the [Spring Data](https://projects.spring.io/spring-data/) project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services.
+This modules provides integration with the [Redis](https://redis.io/) store.
# Docs
-You can find out more details from the [user documentation](http://docs.spring.io/spring-data/data-redis/docs/current/reference/html/) or by browsing the [javadocs](http://docs.spring.io/spring-data/data-redis/docs/current/api/).
+You can find out more details from the [user documentation](https://docs.spring.io/spring-data/data-redis/docs/current/reference/html/) or by browsing the [javadocs](https://docs.spring.io/spring-data/data-redis/docs/current/api/).
# Examples
@@ -41,7 +41,7 @@ If you'd rather like the latest snapshots of the upcoming major version, use our
spring-libs-snapshot
Spring Snapshot Repository
- http://repo.spring.io/libs-snapshot
+ https://repo.spring.io/libs-snapshot
```
@@ -49,8 +49,8 @@ If you'd rather like the latest snapshots of the upcoming major version, use our
```groovy
repositories {
- maven { url "http://repo.spring.io/libs-milestone" }
- maven { url "http://repo.spring.io/libs-snapshot" }
+ maven { url "https://repo.spring.io/libs-milestone" }
+ maven { url "https://repo.spring.io/libs-snapshot" }
}
// used for nightly builds
@@ -68,7 +68,7 @@ dependencies {
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:p="http://www.springframework.org/schema/p"
xsi:schemaLocation="
- http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">
+ http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd">
@@ -115,15 +115,15 @@ You can alternatively use the provided `Makefile` which runs the build plus down
Here are some ways for you to get involved in the community:
-* Get involved with the Spring community on the Stackoverflow. Please help out on the [spring-data-redis](http://stackoverflow.com/questions/tagged/spring-data-redis) tag by responding to questions and joining the debate.
+* Get involved with the Spring community on the Stackoverflow. Please help out on the [spring-data-redis](https://stackoverflow.com/questions/tagged/spring-data-redis) tag by responding to questions and joining the debate.
* Create [JIRA](https://jira.spring.io/browse/DATAREDIS) tickets for bugs and new features and comment and vote on the ones that you are interested in.
* Watch for upcoming articles on Spring by [subscribing](https://spring.io/blog) to spring.io.
Before we accept a non-trivial patch or pull request we will need you to [sign the Contributor License Agreement](https://cla.pivotal.io/sign/spring). Signing the contributor’s agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. If you forget to do so, you'll be reminded when you submit a pull request.
-Github is for social coding: if you want to write code, we encourage contributions through pull requests from [forks of this repository](http://help.github.com/forking/). If you want to contribute code this way, read the Spring Framework [contributor guidelines] (https://github.com/spring-projects/spring-framework/blob/master/CONTRIBUTING.md).
+Github is for social coding: if you want to write code, we encourage contributions through pull requests from [forks of this repository](https://help.github.com/forking/). If you want to contribute code this way, read the Spring Framework [contributor guidelines] (https://github.com/spring-projects/spring-framework/blob/master/CONTRIBUTING.md).
# Staying in touch
-Follow the project team ([@SpringData](http://twitter.com/springdata)) on Twitter. In-depth articles can be
+Follow the project team ([@SpringData](https://twitter.com/springdata)) on Twitter. In-depth articles can be
found at the Spring [team blog](https://spring.io/blog), and releases are announced via our [news feed](https://spring.io/blog/category/news).
diff --git a/src/main/asciidoc/appendix/appendix-schema.adoc b/src/main/asciidoc/appendix/appendix-schema.adoc
index fa3aa7311c..b8f0438471 100644
--- a/src/main/asciidoc/appendix/appendix-schema.adoc
+++ b/src/main/asciidoc/appendix/appendix-schema.adoc
@@ -2,4 +2,4 @@
[appendix]
= Schema
-link:http://www.springframework.org/schema/redis/spring-redis-1.0.xsd[Spring Data Redis Schema (redis-namespace)]
+link:https://www.springframework.org/schema/redis/spring-redis-1.0.xsd[Spring Data Redis Schema (redis-namespace)]
diff --git a/src/main/asciidoc/introduction/getting-started.adoc b/src/main/asciidoc/introduction/getting-started.adoc
index f98f06cb42..7beadeed11 100644
--- a/src/main/asciidoc/introduction/getting-started.adoc
+++ b/src/main/asciidoc/introduction/getting-started.adoc
@@ -11,17 +11,17 @@ As explained in <>, Spring Data Redis (SDR) provides integrati
[[get-started:first-steps:spring]]
=== Learning Spring
-Spring Data uses Spring framework's http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html[core] functionality, such as the http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html[IoC] container, http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html#resources[resource] abstract, and the http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html#aop[AOP] infrastructure. While it is not important to know the Spring APIs, understanding the concepts behind them is important. At a minimum, the idea behind IoC should be familiar. That being said, the more knowledge you have about the Spring, the faster you can pick up Spring Data Redis. In addition to the Spring Framework's comprehensive documentation, there are a lot of articles, blog entries, and books on the matter. The Spring Guides http://spring.io/guides[home page] offer a good place to start. In general, this should be the starting point for developers wanting to try Spring Data Redis.
+Spring Data uses Spring framework's https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html[core] functionality, such as the https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html[IoC] container, https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html#resources[resource] abstract, and the https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/core.html#aop[AOP] infrastructure. While it is not important to know the Spring APIs, understanding the concepts behind them is important. At a minimum, the idea behind IoC should be familiar. That being said, the more knowledge you have about the Spring, the faster you can pick up Spring Data Redis. In addition to the Spring Framework's comprehensive documentation, there are a lot of articles, blog entries, and books on the matter. The Spring Guides https://spring.io/guides[home page] offer a good place to start. In general, this should be the starting point for developers wanting to try Spring Data Redis.
[[get-started:first-steps:nosql]]
=== Learning NoSQL and Key Value Stores
-NoSQL stores have taken the storage world by storm. It is a vast domain with a plethora of solutions, terms, and patterns (to make things worse, even the term itself has multiple http://www.google.com/search?q=nosoql+acronym[meanings]). While some of the principles are common, it is crucial that you be familiar to some degree with the stores supported by SDR. The best way to get acquainted with these solutions is to read their documentation and follow their examples. It usually does not take more then five to ten minutes to go through them and, if you come from an RDMBS-only background, many times these exercises can be eye-openers.
+NoSQL stores have taken the storage world by storm. It is a vast domain with a plethora of solutions, terms, and patterns (to make things worse, even the term itself has multiple https://www.google.com/search?q=nosoql+acronym[meanings]). While some of the principles are common, it is crucial that you be familiar to some degree with the stores supported by SDR. The best way to get acquainted with these solutions is to read their documentation and follow their examples. It usually does not take more then five to ten minutes to go through them and, if you come from an RDMBS-only background, many times these exercises can be eye-openers.
[[get-started:first-steps:samples]]
=== Trying out the Samples
-One can find various samples for key-value stores in the dedicated Spring Data example repo, at https://github.com/spring-projects/spring-data-keyvalue-examples[http://github.com/spring-projects/spring-data-keyvalue-examples]. For Spring Data Redis, you should pay particular attention to the `retwisj` sample, a Twitter-clone built on top of Redis that can be run locally or be deployed into the cloud. See its http://static.springsource.org/spring-data/data-keyvalue/examples/retwisj/current/[documentation], the following blog http://blog.springsource.com/2011/04/27/getting-started-redis-spring-cloud-foundry/[entry] for more information.
+One can find various samples for key-value stores in the dedicated Spring Data example repo, at https://github.com/spring-projects/spring-data-keyvalue-examples[https://github.com/spring-projects/spring-data-keyvalue-examples]. For Spring Data Redis, you should pay particular attention to the `retwisj` sample, a Twitter-clone built on top of Redis that can be run locally or be deployed into the cloud. See its https://docs.spring.io/spring-data/data-keyvalue/examples/retwisj/current/[documentation], the following blog https://spring.io/blog/2011/04/27/getting-started-redis-spring-cloud-foundry/[entry] for more information.
[[get-started:help]]
== Need Help?
@@ -31,23 +31,23 @@ If you encounter issues or you are just looking for advice, use one of the links
[[get-started:help:community]]
=== Community Support
-The Spring Data tag on http://stackoverflow.com/questions/tagged/spring-data[Stack Overflow] is a message board for all Spring Data (not just Redis) users to share information and help each other. Note that registration is needed *only* for posting.
+The Spring Data tag on https://stackoverflow.com/questions/tagged/spring-data[Stack Overflow] is a message board for all Spring Data (not just Redis) users to share information and help each other. Note that registration is needed *only* for posting.
[[get-started:help:professional]]
=== Professional Support
-Professional, from-the-source support, with guaranteed response time, is available from http://www.pivotal.io/[Pivotal Software, Inc.], the company behind Spring Data and Spring.
+Professional, from-the-source support, with guaranteed response time, is available from https://www.pivotal.io/[Pivotal Software, Inc.], the company behind Spring Data and Spring.
[[get-started:up-to-date]]
== Following Development
-For information on the Spring Data source code repository, nightly builds, and snapshot artifacts, see the Spring Data home http://spring.io/spring-data[page].
+For information on the Spring Data source code repository, nightly builds, and snapshot artifacts, see the Spring Data home https://spring.io/spring-data[page].
You can help make Spring Data best serve the needs of the Spring community by interacting with developers on Stack Overflow at either
-http://stackoverflow.com/questions/tagged/spring-data[spring-data] or http://stackoverflow.com/questions/tagged/spring-data-redis[spring-data-redis].
+https://stackoverflow.com/questions/tagged/spring-data[spring-data] or https://stackoverflow.com/questions/tagged/spring-data-redis[spring-data-redis].
If you encounter a bug or want to suggest an improvement (including to this documentation), please create a ticket on the Spring Data issue https://jira.spring.io/browse/DATAREDIS[tracker].
-To stay up to date with the latest news and announcements in the Spring eco system, subscribe to the Spring Community http://spring.io/[Portal].
+To stay up to date with the latest news and announcements in the Spring eco system, subscribe to the Spring Community https://spring.io/[Portal].
-Lastly, you can follow the Spring http://spring.io/blog/[blog] or the project team (http://twitter.com/SpringData[@SpringData]) on Twitter.
+Lastly, you can follow the Spring https://spring.io/blog/[blog] or the project team (https://twitter.com/SpringData[@SpringData]) on Twitter.
diff --git a/src/main/asciidoc/introduction/requirements.adoc b/src/main/asciidoc/introduction/requirements.adoc
index 5db3a31037..58c4b7cd37 100644
--- a/src/main/asciidoc/introduction/requirements.adoc
+++ b/src/main/asciidoc/introduction/requirements.adoc
@@ -1,6 +1,6 @@
[[requirements]]
= Requirements
-Spring Data Redis 2.x binaries require JDK level 8.0 and above and http://projects.spring.io/spring-framework/[Spring Framework] {springVersion} and above.
+Spring Data Redis 2.x binaries require JDK level 8.0 and above and https://projects.spring.io/spring-framework/[Spring Framework] {springVersion} and above.
-In terms of key-value stores, http://redis.io[Redis] 2.6.x or higher is required. Spring Data Redis is currently tested against the latest 4.0 release.
+In terms of key-value stores, https://redis.io[Redis] 2.6.x or higher is required. Spring Data Redis is currently tested against the latest 4.0 release.
diff --git a/src/main/asciidoc/introduction/why-sdr.adoc b/src/main/asciidoc/introduction/why-sdr.adoc
index 1e1689a58d..14dcbbfc2a 100644
--- a/src/main/asciidoc/introduction/why-sdr.adoc
+++ b/src/main/asciidoc/introduction/why-sdr.adoc
@@ -3,6 +3,6 @@
The Spring Framework is the leading full-stack Java/JEE application framework. It provides a lightweight container and a non-invasive programming model enabled by the use of dependency injection, AOP, and portable service abstractions.
-http://en.wikipedia.org/wiki/NoSQL[NoSQL] storage systems provide an alternative to classical RDBMS for horizontal scalability and speed. In terms of implementation, key-value stores represent one of the largest (and oldest) members in the NoSQL space.
+https://en.wikipedia.org/wiki/NoSQL[NoSQL] storage systems provide an alternative to classical RDBMS for horizontal scalability and speed. In terms of implementation, key-value stores represent one of the largest (and oldest) members in the NoSQL space.
The Spring Data Redis (SDR) framework makes it easy to write Spring applications that use the Redis key-value store by eliminating the redundant tasks and boilerplate code required for interacting with the store through Spring's excellent infrastructure support.
diff --git a/src/main/asciidoc/new-features.adoc b/src/main/asciidoc/new-features.adoc
index 6cd6d460d6..98126a3f53 100644
--- a/src/main/asciidoc/new-features.adoc
+++ b/src/main/asciidoc/new-features.adoc
@@ -41,7 +41,7 @@ This section briefly covers items that are new and noteworthy in the latest rele
* Upgrade to Jedis 2.9.
* Upgrade to `Lettuce` 4.2 (Note: Lettuce 4.2 requires Java 8).
-* Support for Redis http://redis.io/commands#geo[GEO] commands.
+* Support for Redis https://redis.io/commands#geo[GEO] commands.
* Support for Geospatial Indexes using Spring Data Repository abstractions (see <>).
* `MappingRedisConverter`-based `HashMapper` implementation (see <>).
* Support for `PartialUpdate` in repositories (see <>).
@@ -51,7 +51,7 @@ This section briefly covers items that are new and noteworthy in the latest rele
[[new-in-1.7.0]]
== New in Spring Data Redis 1.7
-* Support for http://redis.io/topics/cluster-tutorial[RedisCluster].
+* Support for https://redis.io/topics/cluster-tutorial[RedisCluster].
* Support for Spring Data Repository abstractions (see <>).
[[new-in-1-6-0]]
diff --git a/src/main/asciidoc/reference/pipelining.adoc b/src/main/asciidoc/reference/pipelining.adoc
index f2753bff9b..3cec6dfcd6 100644
--- a/src/main/asciidoc/reference/pipelining.adoc
+++ b/src/main/asciidoc/reference/pipelining.adoc
@@ -1,7 +1,7 @@
[[pipeline]]
= Pipelining
-Redis provides support for http://redis.io/topics/pipelining[pipelining], which involves sending multiple commands to the server without waiting for the replies and then reading the replies in a single step. Pipelining can improve performance when you need to send several commands in a row, such as adding many elements to the same List.
+Redis provides support for https://redis.io/topics/pipelining[pipelining], which involves sending multiple commands to the server without waiting for the replies and then reading the replies in a single step. Pipelining can improve performance when you need to send several commands in a row, such as adding many elements to the same List.
Spring Data Redis provides several `RedisTemplate` methods for executing commands in a pipeline. If you do not care about the results of the pipelined operations, you can use the standard `execute` method, passing `true` for the `pipeline` argument. The `executePipelined` methods run the provided `RedisCallback` or `SessionCallback` in a pipeline and return the results, as shown in the following example:
diff --git a/src/main/asciidoc/reference/reactive-redis.adoc b/src/main/asciidoc/reference/reactive-redis.adoc
index f256780d58..3e0b35c35f 100644
--- a/src/main/asciidoc/reference/reactive-redis.adoc
+++ b/src/main/asciidoc/reference/reactive-redis.adoc
@@ -7,7 +7,7 @@ This section covers reactive Redis support and how to get started. Reactive Redi
[[redis:reactive:requirements]]
== Redis Requirements
-Spring Data Redis currently integrates with http://github.com/lettuce-io/lettuce-core[Lettuce] as the only reactive Java connector. https://projectreactor.io/[Project Reactor] is used as reactive composition library.
+Spring Data Redis currently integrates with https://github.com/lettuce-io/lettuce-core[Lettuce] as the only reactive Java connector. https://projectreactor.io/[Project Reactor] is used as reactive composition library.
[[redis:reactive:connectors]]
== Connecting to Redis by Using a Reactive Driver
@@ -18,14 +18,14 @@ One of the first tasks when using Redis and Spring is to connect to the store th
=== Redis Operation Modes
Redis can be run as a standalone server, with <>, or in <> mode.
-http://github.com/lettuce-io/lettuce-core[Lettuce] supports all of the previously mentioned connection types.
+https://github.com/lettuce-io/lettuce-core[Lettuce] supports all of the previously mentioned connection types.
[[redis:reactive:connectors:connection]]
=== `ReactiveRedisConnection` and `ReactiveRedisConnectionFactory`
-`ReactiveRedisConnection` is the core of Redis communication, as it handles the communication with the Redis back-end. It also automatically translates the underlying driver exceptions to Spring's consistent DAO exception http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#dao-exceptions[hierarchy], so you can switch the connectors without any code changes, as the operation semantics remain the same.
+`ReactiveRedisConnection` is the core of Redis communication, as it handles the communication with the Redis back-end. It also automatically translates the underlying driver exceptions to Spring's consistent DAO exception https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#dao-exceptions[hierarchy], so you can switch the connectors without any code changes, as the operation semantics remain the same.
-`ReactiveRedisConnectionFactory` creates active `ReactiveRedisConnection` instances. In addition, the factories act as `PersistenceExceptionTranslator` instances, meaning that, once declared, they let you do transparent exception translation -- for example, exception translation through the use of the `@Repository` annotation and AOP. For more information, see the dedicated http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#orm-exception-translation[section] in the Spring Framework documentation.
+`ReactiveRedisConnectionFactory` creates active `ReactiveRedisConnection` instances. In addition, the factories act as `PersistenceExceptionTranslator` instances, meaning that, once declared, they let you do transparent exception translation -- for example, exception translation through the use of the `@Repository` annotation and AOP. For more information, see the dedicated https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#orm-exception-translation[section] in the Spring Framework documentation.
NOTE: Depending on the underlying configuration, the factory can return a new connection or an existing connection (in case a pool or shared native connection is used).
@@ -70,7 +70,7 @@ For more detailed client configuration tweaks, see https://docs.spring.io/spring
Most users are likely to use `ReactiveRedisTemplate` and its corresponding package, `org.springframework.data.redis.core`. Due to its rich feature set, the template is, in fact, the central class of the Redis module. The template offers a high-level abstraction for Redis interactions. While `ReactiveRedisConnection` offers low-level methods that accept and return binary values (`ByteBuffer`), the template takes care of serialization and connection management, freeing you from dealing with such details.
-Moreover, the template provides operation views (following the grouping from Redis command http://redis.io/commands[reference]) that offer rich, generified interfaces for working against a certain type as described in the following table:
+Moreover, the template provides operation views (following the grouping from Redis command https://redis.io/commands[reference]) that offer rich, generified interfaces for working against a certain type as described in the following table:
.Operational views
[width="80%",cols="<1,<2",options="header"]
diff --git a/src/main/asciidoc/reference/redis-cluster.adoc b/src/main/asciidoc/reference/redis-cluster.adoc
index 7406d17d01..ba0587ba90 100644
--- a/src/main/asciidoc/reference/redis-cluster.adoc
+++ b/src/main/asciidoc/reference/redis-cluster.adoc
@@ -1,7 +1,7 @@
[[cluster]]
= Redis Cluster
-Working with http://redis.io/topics/cluster-spec[Redis Cluster] requires Redis Server version 3.0+. See the http://redis.io/topics/cluster-tutorial[Cluster Tutorial] for more information.
+Working with https://redis.io/topics/cluster-spec[Redis Cluster] requires Redis Server version 3.0+. See the https://redis.io/topics/cluster-tutorial[Cluster Tutorial] for more information.
== Enabling Redis Cluster
diff --git a/src/main/asciidoc/reference/redis-messaging.adoc b/src/main/asciidoc/reference/redis-messaging.adoc
index 1e4bd06364..f746b0eb4f 100644
--- a/src/main/asciidoc/reference/redis-messaging.adoc
+++ b/src/main/asciidoc/reference/redis-messaging.adoc
@@ -87,8 +87,8 @@ Notice how the above implementation of the `MessageDelegate` interface (the abov
+ xsi:schemaLocation="http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd
+ http://www.springframework.org/schema/redis https://www.springframework.org/schema/redis/spring-redis.xsd">
diff --git a/src/main/asciidoc/reference/redis-repositories.adoc b/src/main/asciidoc/reference/redis-repositories.adoc
index 0f1279854c..162fdb7bcd 100644
--- a/src/main/asciidoc/reference/redis-repositories.adoc
+++ b/src/main/asciidoc/reference/redis-repositories.adoc
@@ -379,7 +379,7 @@ public class ApplicationConfig {
[[redis.repositories.indexes]]
== Secondary Indexes
-http://redis.io/topics/indexes[Secondary indexes] are used to enable lookup operations based on native Redis structures. Values are written to the according indexes on every save and are removed when objects are deleted or <>.
+https://redis.io/topics/indexes[Secondary indexes] are used to enable lookup operations based on native Redis structures. Values are written to the according indexes on every save and are removed when objects are deleted or <>.
[[redis.repositories.indexes.simple]]
=== Simple Property Index
@@ -578,7 +578,7 @@ public class TimeToLiveOnMethod {
NOTE: Annotating a property explicitly with `@TimeToLive` reads back the actual `TTL` or `PTTL` value from Redis. -1 indicates that the object has no associated expiration.
-The repository implementation ensures subscription to http://redis.io/topics/notifications[Redis keyspace notifications] via `RedisMessageListenerContainer`.
+The repository implementation ensures subscription to https://redis.io/topics/notifications[Redis keyspace notifications] via `RedisMessageListenerContainer`.
When the expiration is set to a positive value, the corresponding `EXPIRE` command is executed. In addition to persisting the original, a phantom copy is persisted in Redis and set to expire five minutes after the original one. This is done to enable the Repository support to publish `RedisKeyExpiredEvent`, holding the expired value in Spring's `ApplicationEventPublisher` whenever a key expires, even though the original values have already been removed. Expiry events are received on all connected applications that use Spring Data Redis repositories.
diff --git a/src/main/asciidoc/reference/redis-scripting.adoc b/src/main/asciidoc/reference/redis-scripting.adoc
index f17a0a75d8..3c4fdb97fb 100644
--- a/src/main/asciidoc/reference/redis-scripting.adoc
+++ b/src/main/asciidoc/reference/redis-scripting.adoc
@@ -1,7 +1,7 @@
[[scripting]]
= Redis Scripting
-Redis versions 2.6 and higher provide support for execution of Lua scripts through the http://redis.io/commands/eval[eval] and http://redis.io/commands/evalsha[evalsha] commands. Spring Data Redis provides a high-level abstraction for script execution that handles serialization and automatically uses the Redis script cache.
+Redis versions 2.6 and higher provide support for execution of Lua scripts through the https://redis.io/commands/eval[eval] and https://redis.io/commands/evalsha[evalsha] commands. Spring Data Redis provides a high-level abstraction for script execution that handles serialization and automatically uses the Redis script cache.
Scripts can be run by calling the `execute` methods of `RedisTemplate` and `ReactiveRedisTemplate`. Both use a configurable `ScriptExecutor` (or `ReactiveScriptExecutor`) to run the provided script. By default, the `ScriptExecutor` (or `ReactiveScriptExecutor`) takes care of serializing the provided keys and arguments and deserializing the script result. This is done through the key and value serializers of the template. There is an additional overload that lets you pass custom serializers for the script arguments and the result.
@@ -49,4 +49,4 @@ TIP: It is ideal to configure a single instance of `DefaultRedisScript` in your
The `checkAndSet` method above then runs the scripts. Scripts can be run within a `SessionCallback` as part of a transaction or pipeline. See "`<>`" and "`<>`" for more information.
-The scripting support provided by Spring Data Redis also lets you schedule Redis scripts for periodic execution by using the Spring Task and Scheduler abstractions. See the http://projects.spring.io/spring-framework/[Spring Framework] documentation for more details.
+The scripting support provided by Spring Data Redis also lets you schedule Redis scripts for periodic execution by using the Spring Task and Scheduler abstractions. See the https://projects.spring.io/spring-framework/[Spring Framework] documentation for more details.
diff --git a/src/main/asciidoc/reference/redis-transactions.adoc b/src/main/asciidoc/reference/redis-transactions.adoc
index 024b7d4af1..203e8ed1a6 100644
--- a/src/main/asciidoc/reference/redis-transactions.adoc
+++ b/src/main/asciidoc/reference/redis-transactions.adoc
@@ -1,7 +1,7 @@
[[tx]]
= Redis Transactions
-Redis provides support for http://redis.io/topics/transactions[transactions] through the `multi`, `exec`, and `discard` commands. These operations are available on `RedisTemplate`. However, `RedisTemplate` is not guaranteed to execute all operations in the transaction with the same connection.
+Redis provides support for https://redis.io/topics/transactions[transactions] through the `multi`, `exec`, and `discard` commands. These operations are available on `RedisTemplate`. However, `RedisTemplate` is not guaranteed to execute all operations in the transaction with the same connection.
Spring Data Redis provides the `SessionCallback` interface for use when multiple operations need to be performed with the same `connection`, such as when using Redis transactions. The following example uses the `multi` method:
@@ -63,7 +63,7 @@ public class RedisTxContextConfiguration {
}
}
----
-<1> Configures a Spring Context to enable http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#transaction-declarative[declarative transaction management].
+<1> Configures a Spring Context to enable https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#transaction-declarative[declarative transaction management].
<2> Configures `RedisTemplate` to participate in transactions by binding connections to the current thread.
<3> Transaction management requires a `PlatformTransactionManager`. Spring Data Redis does not ship with a `PlatformTransactionManager` implementation. Assuming your application uses JDBC, Spring Data Redis can participate in transactions by using existing transaction managers.
====
diff --git a/src/main/asciidoc/reference/redis.adoc b/src/main/asciidoc/reference/redis.adoc
index 6f2bc36e7f..3d57c271e0 100644
--- a/src/main/asciidoc/reference/redis.adoc
+++ b/src/main/asciidoc/reference/redis.adoc
@@ -2,7 +2,7 @@
= Redis support
:referenceDir: .
-One of the key-value stores supported by Spring Data is http://redis.io[Redis]. To quote the Redis project home page:
+One of the key-value stores supported by Spring Data is https://redis.io[Redis]. To quote the Redis project home page:
[quote]
Redis is an advanced key-value store. It is similar to memcached but the dataset is not volatile, and values can be strings, exactly like in memcached, but also lists, sets, and ordered sets. All this data types can be manipulated with atomic operations to push/pop elements, add/remove elements, perform server side union, intersection, difference between sets, and so forth. Redis supports different kind of sorting abilities.
@@ -12,7 +12,7 @@ Spring Data Redis provides easy configuration and access to Redis from Spring ap
[[redis:requirements]]
== Redis Requirements
-Spring Redis requires Redis 2.6 or above and Spring Data Redis integrates with http://github.com/lettuce-io/lettuce-core[Lettuce] and http://github.com/xetorthio/jedis[Jedis], two popular open-source Java libraries for Redis.
+Spring Redis requires Redis 2.6 or above and Spring Data Redis integrates with https://github.com/lettuce-io/lettuce-core[Lettuce] and https://github.com/xetorthio/jedis[Jedis], two popular open-source Java libraries for Redis.
[[redis:architecture]]
== Redis Support High-level View
@@ -27,11 +27,11 @@ One of the first tasks when using Redis and Spring is to connect to the store th
[[redis:connectors:connection]]
=== RedisConnection and RedisConnectionFactory
-`RedisConnection` provides the core building block for Redis communication, as it handles the communication with the Redis back end. It also automatically translates the underlying connecting library exceptions to Spring's consistent DAO exception http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#dao-exceptions[hierarchy] so that you can switch the connectors without any code changes, as the operation semantics remain the same.
+`RedisConnection` provides the core building block for Redis communication, as it handles the communication with the Redis back end. It also automatically translates the underlying connecting library exceptions to Spring's consistent DAO exception https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#dao-exceptions[hierarchy] so that you can switch the connectors without any code changes, as the operation semantics remain the same.
NOTE: For the corner cases where the native library API is required, `RedisConnection` provides a dedicated method (`getNativeConnection`) that returns the raw, underlying object used for communication.
-Active `RedisConnection` objects are created through `RedisConnectionFactory`. In addition, the factory acts as `PersistenceExceptionTranslator` objects, meaning that, once declared, they let you do transparent exception translation. For example, you can do exception translation through the use of the `@Repository` annotation and AOP. For more information, see the dedicated http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#orm-exception-translation[section] in the Spring Framework documentation.
+Active `RedisConnection` objects are created through `RedisConnectionFactory`. In addition, the factory acts as `PersistenceExceptionTranslator` objects, meaning that, once declared, they let you do transparent exception translation. For example, you can do exception translation through the use of the `@Repository` annotation and AOP. For more information, see the dedicated https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#orm-exception-translation[section] in the Spring Framework documentation.
NOTE: Depending on the underlying configuration, the factory can return a new connection or an existing connection (when a pool or shared native connection is used).
@@ -42,7 +42,7 @@ IMPORTANT: Unfortunately, currently, not all connectors support all Redis featur
[[redis:connectors:lettuce]]
=== Configuring the Lettuce Connector
-https://github.com/lettuce-io/lettuce-core[Lettuce] is a http://netty.io/[Netty]-based open-source connector supported by Spring Data Redis through the `org.springframework.data.redis.connection.lettuce` package. The following example shows how to create a new Lettuce connection factory:
+https://github.com/lettuce-io/lettuce-core[Lettuce] is a https://netty.io/[Netty]-based open-source connector supported by Spring Data Redis through the `org.springframework.data.redis.connection.lettuce` package. The following example shows how to create a new Lettuce connection factory:
[source,java]
----
@@ -59,7 +59,7 @@ class AppConfig {
There are also a few Lettuce-specific connection parameters that can be tweaked. By default, all `LettuceConnection` instances created by the `LettuceConnectionFactory` share the same thread-safe native connection for all non-blocking and non-transactional operations. To use a dedicated connection each time, set `shareNativeConnection` to `false`. `LettuceConnectionFactory` can also be configured to use a `LettucePool` for pooling blocking and transactional connections or all connections if `shareNativeConnection` is set to `false`.
-Lettuce integrates with Netty's http://netty.io/wiki/native-transports.html[native transports], letting you use Unix domain sockets to communicate with Redis. Make sure to include the appropriate native transport dependencies that match your runtime environment. The following example shows how to create a Lettuce Connection factory for a Unix domain socket at `/var/run/redis.sock`:
+Lettuce integrates with Netty's https://netty.io/wiki/native-transports.html[native transports], letting you use Unix domain sockets to communicate with Redis. Make sure to include the appropriate native transport dependencies that match your runtime environment. The following example shows how to create a Lettuce Connection factory for a Unix domain socket at `/var/run/redis.sock`:
[source,java]
----
@@ -79,7 +79,7 @@ NOTE: Netty currently supports the epoll (Linux) and kqueue (BSD/macOS) interfac
[[redis:connectors:jedis]]
=== Configuring the Jedis Connector
-http://github.com/xetorthio/jedis[Jedis] is a community-driven connector supported by the Spring Data Redis module through the `org.springframework.data.redis.connection.jedis` package. In its simplest form, the Jedis configuration looks as follow:
+https://github.com/xetorthio/jedis[Jedis] is a community-driven connector supported by the Spring Data Redis module through the `org.springframework.data.redis.connection.jedis` package. In its simplest form, the Jedis configuration looks as follow:
[source,java]
----
@@ -138,7 +138,7 @@ TIP: For environments reporting non-public addresses through the `INFO` command
[[redis:sentinel]]
== Redis Sentinel Support
-For dealing with high-availability Redis, Spring Data Redis has support for http://redis.io/topics/sentinel[Redis Sentinel], using `RedisSentinelConfiguration`, as shown in the following example:
+For dealing with high-availability Redis, Spring Data Redis has support for https://redis.io/topics/sentinel[Redis Sentinel], using `RedisSentinelConfiguration`, as shown in the following example:
[source,java]
----
@@ -183,7 +183,7 @@ Sometimes, direct interaction with one of the Sentinels is required. Using `Redi
Most users are likely to use `RedisTemplate` and its corresponding package, `org.springframework.data.redis.core`. The template is, in fact, the central class of the Redis module, due to its rich feature set. The template offers a high-level abstraction for Redis interactions. While `RedisConnection` offers low-level methods that accept and return binary values (`byte` arrays), the template takes care of serialization and connection management, freeing the user from dealing with such details.
-Moreover, the template provides operations views (following the grouping from the Redis command http://redis.io/commands[reference]) that offer rich, generified interfaces for working against a certain type or certain key (through the `KeyBound` interfaces) as described in the following table:
+Moreover, the template provides operations views (following the grouping from the Redis command https://redis.io/commands[reference]) that offer rich, generified interfaces for working against a certain type or certain key (through the `KeyBound` interfaces) as described in the following table:
.Operational views
[width="80%",cols="<1,<2",options="header"]
@@ -251,7 +251,7 @@ For cases where you need a certain template view, declare the view as a dependen
+ xsi:schemaLocation="http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd">
@@ -290,7 +290,7 @@ Since it is quite common for the keys and values stored in Redis to be `java.lan
+ xsi:schemaLocation="http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd">
@@ -347,7 +347,7 @@ Multiple implementations are available (including two that have been already men
* `JdkSerializationRedisSerializer`, which is used by default for `RedisCache` and `RedisTemplate`.
* the `StringRedisSerializer`.
-However one can use `OxmSerializer` for Object/XML mapping through Spring http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#oxm[OXM] support or `Jackson2JsonRedisSerializer` or `GenericJackson2JsonRedisSerializer` for storing data in http://en.wikipedia.org/wiki/JSON[JSON] format.
+However one can use `OxmSerializer` for Object/XML mapping through Spring https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/data-access.html#oxm[OXM] support or `Jackson2JsonRedisSerializer` or `GenericJackson2JsonRedisSerializer` for storing data in https://en.wikipedia.org/wiki/JSON[JSON] format.
Do note that the storage format is not limited only to values. It can be used for keys, values, or hashes without any restrictions.
@@ -358,14 +358,14 @@ By default, `RedisCache` and `RedisTemplate` are configured to use Java native s
If you are concerned about security vulnerabilities due to Java serialization, consider the general-purpose serialization filter mechanism at the core JVM level, originally developed for JDK 9 but backported to JDK 8, 7, and 6:
* https://blogs.oracle.com/java-platform-group/entry/incoming_filter_serialization_data_a[Filter Incoming Serialization Data].
-* http://openjdk.java.net/jeps/290[JEP 290].
+* https://openjdk.java.net/jeps/290[JEP 290].
* https://www.owasp.org/index.php/Deserialization_of_untrusted_data[OWASP: Deserialization of untrusted data].
====
[[redis.hashmappers.root]]
== Hash mapping
-Data can be stored by using various data structures within Redis. `Jackson2JsonRedisSerializer` can convert objects in http://en.wikipedia.org/wiki/JSON[JSON] format. Ideally, JSON can be stored as a value by using plain keys. You can achieve a more sophisticated mapping of structured objects by using Redis hashes. Spring Data Redis offers various strategies for mapping data to hashes (depending on the use case):
+Data can be stored by using various data structures within Redis. `Jackson2JsonRedisSerializer` can convert objects in https://en.wikipedia.org/wiki/JSON[JSON] format. Ideally, JSON can be stored as a value by using plain keys. You can achieve a more sophisticated mapping of structured objects by using Redis hashes. Spring Data Redis offers various strategies for mapping data to hashes (depending on the use case):
* Direct mapping, by using `HashOperations` and a <>
* Using <>
@@ -377,7 +377,7 @@ Hash mappers are converters of map objects to a `Map` and back. `HashMappe
Multiple implementations are available:
-* `BeanUtilsHashMapper` using Spring's http://docs.spring.io/spring/docs/{springVersion}/javadoc-api/org/springframework/beans/BeanUtils.html[BeanUtils].
+* `BeanUtilsHashMapper` using Spring's https://docs.spring.io/spring/docs/{springVersion}/javadoc-api/org/springframework/beans/BeanUtils.html[BeanUtils].
* `ObjectHashMapper` using <>.
* <> using https://github.com/FasterXML/jackson[FasterXML Jackson].
@@ -494,7 +494,7 @@ include::{referenceDir}/redis-scripting.adoc[]
[[redis:support]]
== Support Classes
-Package `org.springframework.data.redis.support` offers various reusable components that rely on Redis as a backing store. Currently, the package contains various JDK-based interface implementations on top of Redis, such as http://download.oracle.com/javase/8/docs/api/java/util/concurrent/atomic/package-summary.html[atomic] counters and JDK http://download.oracle.com/javase/8/docs/api/java/util/Collection.html[Collections].
+Package `org.springframework.data.redis.support` offers various reusable components that rely on Redis as a backing store. Currently, the package contains various JDK-based interface implementations on top of Redis, such as https://download.oracle.com/javase/8/docs/api/java/util/concurrent/atomic/package-summary.html[atomic] counters and JDK https://download.oracle.com/javase/8/docs/api/java/util/Collection.html[Collections].
The atomic counters make it easy to wrap Redis key incrementation while the collections allow easy management of Redis keys with minimal storage exposure or API leakage. In particular, the `RedisSet` and `RedisZSet` interfaces offer easy access to the set operations supported by Redis, such as `intersection` and `union`. `RedisList` implements the `List`, `Queue`, and `Deque` contracts (and their equivalent blocking siblings) on top of Redis, exposing the storage as a FIFO (First-In-First-Out), LIFO (Last-In-First-Out) or capped collection with minimal configuration. The following example shows the configuration for a bean that uses a `RedisList`:
@@ -504,7 +504,7 @@ The atomic counters make it easy to wrap Redis key incrementation while the coll
+ http://www.springframework.org/schema/beans https://www.springframework.org/schema/beans/spring-beans.xsd">
@@ -536,7 +536,7 @@ As shown in the preceding example, the consuming code is decoupled from the actu
NOTE: Changed in 2.0
-Spring Redis provides an implementation for the Spring http://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/integration.html#cache[cache abstraction] through the `org.springframework.data.redis.cache` package. To use Redis as a backing implementation, add `RedisCacheManager` to your configuration, as follows:
+Spring Redis provides an implementation for the Spring https://docs.spring.io/spring/docs/{springVersion}/spring-framework-reference/integration.html#cache[cache abstraction] through the `org.springframework.data.redis.cache` package. To use Redis as a backing implementation, add `RedisCacheManager` to your configuration, as follows:
[source,java]
----
diff --git a/src/main/java/org/springframework/data/redis/connection/BitFieldSubCommands.java b/src/main/java/org/springframework/data/redis/connection/BitFieldSubCommands.java
index 82cb4e4753..4a927975e8 100644
--- a/src/main/java/org/springframework/data/redis/connection/BitFieldSubCommands.java
+++ b/src/main/java/org/springframework/data/redis/connection/BitFieldSubCommands.java
@@ -328,7 +328,7 @@ public interface BitFieldSubCommand {
/**
* Offset used inside a {@link BitFieldSubCommand}. Can be zero or type based. See
- * Bits and positional offsets in the
+ * Bits and positional offsets in the
* Redis reference.
*
* @author Christoph Strobl
diff --git a/src/main/java/org/springframework/data/redis/connection/ReactiveGeoCommands.java b/src/main/java/org/springframework/data/redis/connection/ReactiveGeoCommands.java
index 092dc0ae1b..1e11af6488 100644
--- a/src/main/java/org/springframework/data/redis/connection/ReactiveGeoCommands.java
+++ b/src/main/java/org/springframework/data/redis/connection/ReactiveGeoCommands.java
@@ -57,7 +57,7 @@ public interface ReactiveGeoCommands {
* {@code GEOADD} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEOADD
+ * @see Redis Documentation: GEOADD
*/
class GeoAddCommand extends KeyCommand {
@@ -121,7 +121,7 @@ public List> getGeoLocations() {
* @param point must not be {@literal null}.
* @param member must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOADD
+ * @see Redis Documentation: GEOADD
*/
default Mono geoAdd(ByteBuffer key, Point point, ByteBuffer member) {
@@ -138,7 +138,7 @@ default Mono geoAdd(ByteBuffer key, Point point, ByteBuffer member) {
* @param key must not be {@literal null}.
* @param location must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOADD
+ * @see Redis Documentation: GEOADD
*/
default Mono geoAdd(ByteBuffer key, GeoLocation location) {
@@ -154,7 +154,7 @@ default Mono geoAdd(ByteBuffer key, GeoLocation location) {
* @param key must not be {@literal null}.
* @param locations must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOADD
+ * @see Redis Documentation: GEOADD
*/
default Mono geoAdd(ByteBuffer key, Collection> locations) {
@@ -169,7 +169,7 @@ default Mono geoAdd(ByteBuffer key, Collection> lo
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOADD
+ * @see Redis Documentation: GEOADD
*/
Flux> geoAdd(Publisher commands);
@@ -177,7 +177,7 @@ default Mono geoAdd(ByteBuffer key, Collection> lo
* {@code GEODIST} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEODIST
+ * @see Redis Documentation: GEODIST
*/
class GeoDistCommand extends KeyCommand {
@@ -306,7 +306,7 @@ public Optional getMetric() {
* @param from must not be {@literal null}.
* @param to must not be {@literal null}.
* @return
- * @see Redis Documentation: GEODIST
+ * @see Redis Documentation: GEODIST
*/
default Mono geoDist(ByteBuffer key, ByteBuffer from, ByteBuffer to) {
return geoDist(key, from, to, DistanceUnit.METERS);
@@ -320,7 +320,7 @@ default Mono geoDist(ByteBuffer key, ByteBuffer from, ByteBuffer to) {
* @param to must not be {@literal null}.
* @param metric must not be {@literal null}.
* @return
- * @see Redis Documentation: GEODIST
+ * @see Redis Documentation: GEODIST
*/
default Mono geoDist(ByteBuffer key, ByteBuffer from, ByteBuffer to, Metric metric) {
@@ -339,7 +339,7 @@ default Mono geoDist(ByteBuffer key, ByteBuffer from, ByteBuffer to, M
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: GEODIST
+ * @see Redis Documentation: GEODIST
*/
Flux> geoDist(Publisher commands);
@@ -347,7 +347,7 @@ default Mono geoDist(ByteBuffer key, ByteBuffer from, ByteBuffer to, M
* {@code GEOHASH} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEOHASH
+ * @see Redis Documentation: GEOHASH
*/
class GeoHashCommand extends KeyCommand {
@@ -413,7 +413,7 @@ public List getMembers() {
* @param key must not be {@literal null}.
* @param member must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOHASH
+ * @see Redis Documentation: GEOHASH
*/
default Mono geoHash(ByteBuffer key, ByteBuffer member) {
@@ -429,7 +429,7 @@ default Mono geoHash(ByteBuffer key, ByteBuffer member) {
* @param key must not be {@literal null}.
* @param members must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOHASH
+ * @see Redis Documentation: GEOHASH
*/
default Mono> geoHash(ByteBuffer key, Collection members) {
@@ -446,7 +446,7 @@ default Mono> geoHash(ByteBuffer key, Collection member
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOHASH
+ * @see Redis Documentation: GEOHASH
*/
Flux> geoHash(Publisher commands);
@@ -454,7 +454,7 @@ default Mono> geoHash(ByteBuffer key, Collection member
* {@code GEOPOS} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEOPOS
+ * @see Redis Documentation: GEOPOS
*/
class GeoPosCommand extends KeyCommand {
@@ -520,7 +520,7 @@ public List getMembers() {
* @param key must not be {@literal null}.
* @param member must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOPOS
+ * @see Redis Documentation: GEOPOS
*/
default Mono geoPos(ByteBuffer key, ByteBuffer member) {
@@ -536,7 +536,7 @@ default Mono geoPos(ByteBuffer key, ByteBuffer member) {
* @param key must not be {@literal null}.
* @param members must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOPOS
+ * @see Redis Documentation: GEOPOS
*/
default Mono> geoPos(ByteBuffer key, Collection members) {
@@ -551,7 +551,7 @@ default Mono> geoPos(ByteBuffer key, Collection members)
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: GEOPOS
+ * @see Redis Documentation: GEOPOS
*/
Flux> geoPos(Publisher commands);
@@ -559,7 +559,7 @@ default Mono> geoPos(ByteBuffer key, Collection members)
* {@code GEORADIUS} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEORADIUS
+ * @see Redis Documentation: GEORADIUS
*/
class GeoRadiusCommand extends KeyCommand {
@@ -868,7 +868,7 @@ private GeoRadiusCommandArgs cloneArgs() {
* @param key must not be {@literal null}.
* @param circle must not be {@literal null}.
* @return
- * @see Redis Documentation: GEORADIUS
+ * @see Redis Documentation: GEORADIUS
*/
default Flux>> geoRadius(ByteBuffer key, Circle circle) {
return geoRadius(key, circle, GeoRadiusCommandArgs.newGeoRadiusArgs());
@@ -881,7 +881,7 @@ default Flux>> geoRadius(ByteBuffer key, Circl
* @param circle must not be {@literal null}.
* @param geoRadiusArgs must not be {@literal null}.
* @return
- * @see Redis Documentation: GEORADIUS
+ * @see Redis Documentation: GEORADIUS
*/
default Flux>> geoRadius(ByteBuffer key, Circle circle,
GeoRadiusCommandArgs geoRadiusArgs) {
@@ -899,7 +899,7 @@ default Flux>> geoRadius(ByteBuffer key, Circl
*
* @param commands
* @return
- * @see Redis Documentation: GEORADIUS
+ * @see Redis Documentation: GEORADIUS
*/
Flux>>>> geoRadius(
Publisher commands);
@@ -908,7 +908,7 @@ Flux>>>
* {@code GEORADIUSBYMEMBER} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: GEORADIUSBYMEMBER
+ * @see Redis Documentation: GEORADIUSBYMEMBER
*/
class GeoRadiusByMemberCommand extends KeyCommand {
@@ -1201,7 +1201,7 @@ private GeoRadiusCommandArgs cloneArgs() {
* @param key must not be {@literal null}.
* @param member must not be {@literal null}.
* @return
- * @see Redis Documentation: GEORADIUSBYMEMBER
+ * @see Redis Documentation: GEORADIUSBYMEMBER
*/
default Flux>> geoRadiusByMember(ByteBuffer key, ByteBuffer member,
Distance distance) {
@@ -1215,7 +1215,7 @@ default Flux>> geoRadiusByMember(ByteBuffer ke
* @param member must not be {@literal null}.
* @param geoRadiusArgs must not be {@literal null}.
* @return
- * @see Redis Documentation: GEORADIUSBYMEMBER
+ * @see Redis Documentation: GEORADIUSBYMEMBER
*/
default Flux>> geoRadiusByMember(ByteBuffer key, ByteBuffer member,
Distance distance, GeoRadiusCommandArgs geoRadiusArgs) {
@@ -1235,7 +1235,7 @@ default Flux>> geoRadiusByMember(ByteBuffer ke
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: GEORADIUSBYMEMBER
+ * @see Redis Documentation: GEORADIUSBYMEMBER
*/
Flux>>>> geoRadiusByMember(
Publisher commands);
diff --git a/src/main/java/org/springframework/data/redis/connection/ReactiveHashCommands.java b/src/main/java/org/springframework/data/redis/connection/ReactiveHashCommands.java
index e52ad3781a..70aafea393 100644
--- a/src/main/java/org/springframework/data/redis/connection/ReactiveHashCommands.java
+++ b/src/main/java/org/springframework/data/redis/connection/ReactiveHashCommands.java
@@ -51,7 +51,7 @@ public interface ReactiveHashCommands {
* {@literal HSET} {@link Command}.
*
* @author Christoph Strobl
- * @see Redis Documentation: HSET
+ * @see Redis Documentation: HSET
*/
class HSetCommand extends KeyCommand {
@@ -154,7 +154,7 @@ public Map getFieldValueMap() {
* @param field must not be {@literal null}.
* @param value must not be {@literal null}.
* @return
- * @see Redis Documentation: HSET
+ * @see Redis Documentation: HSET
*/
default Mono hSet(ByteBuffer key, ByteBuffer field, ByteBuffer value) {
@@ -172,7 +172,7 @@ default Mono hSet(ByteBuffer key, ByteBuffer field, ByteBuffer value) {
* @param field must not be {@literal null}.
* @param value must not be {@literal null}.
* @return
- * @see Redis Documentation: HSETNX
+ * @see Redis Documentation: HSETNX
*/
default Mono hSetNX(ByteBuffer key, ByteBuffer field, ByteBuffer value) {
@@ -190,7 +190,7 @@ default Mono hSetNX(ByteBuffer key, ByteBuffer field, ByteBuffer value)
* @param key must not be {@literal null}.
* @param fieldValueMap must not be {@literal null}.
* @return
- * @see Redis Documentation: HMSET
+ * @see Redis Documentation: HMSET
*/
default Mono hMSet(ByteBuffer key, Map fieldValueMap) {
@@ -205,7 +205,7 @@ default Mono hMSet(ByteBuffer key, Map fieldVal
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HSET
+ * @see Redis Documentation: HSET
*/
Flux> hSet(Publisher commands);
@@ -213,7 +213,7 @@ default Mono hMSet(ByteBuffer key, Map fieldVal
* {@literal HGET} {@link Command}.
*
* @author Christoph Strobl
- * @see Redis Documentation: HGET
+ * @see Redis Documentation: HGET
*/
class HGetCommand extends KeyCommand {
@@ -279,7 +279,7 @@ public List getFields() {
* @param key must not be {@literal null}.
* @param field must not be {@literal null}.
* @return
- * @see Redis Documentation: HGET
+ * @see Redis Documentation: HGET
*/
default Mono hGet(ByteBuffer key, ByteBuffer field) {
return hMGet(key, Collections.singletonList(field)).map(val -> val.isEmpty() ? null : val.iterator().next());
@@ -291,7 +291,7 @@ default Mono hGet(ByteBuffer key, ByteBuffer field) {
* @param key must not be {@literal null}.
* @param fields must not be {@literal null}.
* @return
- * @see Redis Documentation: HMGET
+ * @see Redis Documentation: HMGET
*/
default Mono> hMGet(ByteBuffer key, Collection fields) {
@@ -306,7 +306,7 @@ default Mono> hMGet(ByteBuffer key, Collection fiel
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HMGET
+ * @see Redis Documentation: HMGET
*/
Flux> hMGet(Publisher commands);
@@ -314,7 +314,7 @@ default Mono> hMGet(ByteBuffer key, Collection fiel
* {@literal HEXISTS} {@link Command}.
*
* @author Christoph Strobl
- * @see Redis Documentation: HEXISTS
+ * @see Redis Documentation: HEXISTS
*/
class HExistsCommand extends KeyCommand {
@@ -367,7 +367,7 @@ public ByteBuffer getField() {
* @param key must not be {@literal null}.
* @param field must not be {@literal null}.
* @return
- * @see Redis Documentation: HEXISTS
+ * @see Redis Documentation: HEXISTS
*/
default Mono hExists(ByteBuffer key, ByteBuffer field) {
@@ -382,13 +382,13 @@ default Mono hExists(ByteBuffer key, ByteBuffer field) {
*
* @param commands
* @return
- * @see Redis Documentation: HEXISTS
+ * @see Redis Documentation: HEXISTS
*/
Flux> hExists(Publisher commands);
/**
* @author Christoph Strobl
- * @see Redis Documentation: HDEL
+ * @see Redis Documentation: HDEL
*/
class HDelCommand extends KeyCommand {
@@ -454,7 +454,7 @@ public List getFields() {
* @param key must not be {@literal null}.
* @param field must not be {@literal null}.
* @return
- * @see Redis Documentation: HDEL
+ * @see Redis Documentation: HDEL
*/
default Mono hDel(ByteBuffer key, ByteBuffer field) {
@@ -469,7 +469,7 @@ default Mono hDel(ByteBuffer key, ByteBuffer field) {
* @param key must not be {@literal null}.
* @param fields must not be {@literal null}.
* @return
- * @see Redis Documentation: HDEL
+ * @see Redis Documentation: HDEL
*/
default Mono hDel(ByteBuffer key, Collection fields) {
@@ -484,7 +484,7 @@ default Mono hDel(ByteBuffer key, Collection fields) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HDEL
+ * @see Redis Documentation: HDEL
*/
Flux> hDel(Publisher commands);
@@ -493,7 +493,7 @@ default Mono hDel(ByteBuffer key, Collection fields) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: HLEN
+ * @see Redis Documentation: HLEN
*/
default Mono hLen(ByteBuffer key) {
@@ -507,7 +507,7 @@ default Mono hLen(ByteBuffer key) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HLEN
+ * @see Redis Documentation: HLEN
*/
Flux> hLen(Publisher commands);
@@ -516,7 +516,7 @@ default Mono hLen(ByteBuffer key) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: HKEYS
+ * @see Redis Documentation: HKEYS
*/
default Flux hKeys(ByteBuffer key) {
@@ -530,7 +530,7 @@ default Flux hKeys(ByteBuffer key) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HKEYS
+ * @see Redis Documentation: HKEYS
*/
Flux>> hKeys(Publisher commands);
@@ -539,7 +539,7 @@ default Flux hKeys(ByteBuffer key) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: HVALS
+ * @see Redis Documentation: HVALS
*/
default Flux hVals(ByteBuffer key) {
@@ -553,7 +553,7 @@ default Flux hVals(ByteBuffer key) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HVALS
+ * @see Redis Documentation: HVALS
*/
Flux>> hVals(Publisher commands);
@@ -562,7 +562,7 @@ default Flux hVals(ByteBuffer key) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: HGETALL
+ * @see Redis Documentation: HGETALL
*/
default Flux> hGetAll(ByteBuffer key) {
@@ -576,7 +576,7 @@ default Flux> hGetAll(ByteBuffer key) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: HGETALL
+ * @see Redis Documentation: HGETALL
*/
Flux>>> hGetAll(Publisher commands);
@@ -587,7 +587,7 @@ default Flux> hGetAll(ByteBuffer key) {
* @param key must not be {@literal null}.
* @return the {@link Flux} emitting {@link java.util.Map.Entry entries} one by one.
* @throws IllegalArgumentException in case the given key is {@literal null}.
- * @see Redis Documentation: HSCAN
+ * @see Redis Documentation: HSCAN
* @since 2.1
*/
default Flux> hScan(ByteBuffer key) {
@@ -602,7 +602,7 @@ default Flux> hScan(ByteBuffer key) {
* @param options must not be {@literal null}. Use {@link ScanOptions#NONE} instead.
* @return the {@link Flux} emitting the raw {@link java.util.Map.Entry entries} one by one.
* @throws IllegalArgumentException in case one of the required arguments is {@literal null}.
- * @see Redis Documentation: HSCAN
+ * @see Redis Documentation: HSCAN
* @since 2.1
*/
default Flux> hScan(ByteBuffer key, ScanOptions options) {
@@ -617,14 +617,14 @@ default Flux> hScan(ByteBuffer key, ScanOption
*
* @param commands must not be {@literal null}.
* @return the {@link Flux} emitting {@link CommandResponse} one by one.
- * @see Redis Documentation: HSCAN
+ * @see Redis Documentation: HSCAN
* @since 2.1
*/
Flux>>> hScan(Publisher commands);
/**
* @author Christoph Strobl
- * @see Redis Documentation: HSTRLEN
+ * @see Redis Documentation: HSTRLEN
* @since 2.1
*/
class HStrLenCommand extends KeyCommand {
diff --git a/src/main/java/org/springframework/data/redis/connection/ReactiveHyperLogLogCommands.java b/src/main/java/org/springframework/data/redis/connection/ReactiveHyperLogLogCommands.java
index 6cb87d50f6..616b3f0a25 100644
--- a/src/main/java/org/springframework/data/redis/connection/ReactiveHyperLogLogCommands.java
+++ b/src/main/java/org/springframework/data/redis/connection/ReactiveHyperLogLogCommands.java
@@ -44,7 +44,7 @@ public interface ReactiveHyperLogLogCommands {
* {@code PFADD} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: PFADD
+ * @see Redis Documentation: PFADD
*/
class PfAddCommand extends KeyCommand {
@@ -109,7 +109,7 @@ public List getValues() {
* @param key must not be {@literal null}.
* @param value must not be {@literal null}.
* @return
- * @see Redis Documentation: PFADD
+ * @see Redis Documentation: PFADD
*/
default Mono pfAdd(ByteBuffer key, ByteBuffer value) {
@@ -124,7 +124,7 @@ default Mono pfAdd(ByteBuffer key, ByteBuffer value) {
* @param key must not be {@literal null}.
* @param values must not be {@literal null}.
* @return
- * @see Redis Documentation: PFADD
+ * @see Redis Documentation: PFADD
*/
default Mono pfAdd(ByteBuffer key, Collection values) {
@@ -139,7 +139,7 @@ default Mono pfAdd(ByteBuffer key, Collection values) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: PFADD
+ * @see Redis Documentation: PFADD
*/
Flux> pfAdd(Publisher commands);
@@ -147,7 +147,7 @@ default Mono pfAdd(ByteBuffer key, Collection values) {
* {@code PFCOUNT} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: PFCOUNT
+ * @see Redis Documentation: PFCOUNT
*/
class PfCountCommand implements Command {
@@ -206,7 +206,7 @@ public ByteBuffer getKey() {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: PFCOUNT
+ * @see Redis Documentation: PFCOUNT
*/
default Mono pfCount(ByteBuffer key) {
@@ -220,7 +220,7 @@ default Mono pfCount(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: PFCOUNT
+ * @see Redis Documentation: PFCOUNT
*/
default Mono pfCount(Collection keys) {
@@ -234,7 +234,7 @@ default Mono pfCount(Collection keys) {
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: PFCOUNT
+ * @see Redis Documentation: PFCOUNT
*/
Flux> pfCount(Publisher commands);
@@ -242,7 +242,7 @@ default Mono pfCount(Collection keys) {
* {@code PFMERGE} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: PFMERGE
+ * @see Redis Documentation: PFMERGE
*/
class PfMergeCommand extends KeyCommand {
@@ -295,7 +295,7 @@ public List getSourceKeys() {
* @param destinationKey must not be {@literal null}.
* @param sourceKeys must not be {@literal null}.
* @return
- * @see Redis Documentation: PFMERGE
+ * @see Redis Documentation: PFMERGE
*/
default Mono pfMerge(ByteBuffer destinationKey, Collection sourceKeys) {
@@ -311,7 +311,7 @@ default Mono pfMerge(ByteBuffer destinationKey, Collection
*
* @param commands must not be {@literal null}.
* @return
- * @see Redis Documentation: PFMERGE
+ * @see Redis Documentation: PFMERGE
*/
Flux> pfMerge(Publisher commands);
}
diff --git a/src/main/java/org/springframework/data/redis/connection/ReactiveKeyCommands.java b/src/main/java/org/springframework/data/redis/connection/ReactiveKeyCommands.java
index c2b9ffc5a3..a3ec9365b7 100644
--- a/src/main/java/org/springframework/data/redis/connection/ReactiveKeyCommands.java
+++ b/src/main/java/org/springframework/data/redis/connection/ReactiveKeyCommands.java
@@ -48,7 +48,7 @@ public interface ReactiveKeyCommands {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: EXISTS
+ * @see Redis Documentation: EXISTS
*/
default Mono exists(ByteBuffer key) {
@@ -62,7 +62,7 @@ default Mono exists(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: EXISTS
+ * @see Redis Documentation: EXISTS
*/
Flux> exists(Publisher keys);
@@ -71,7 +71,7 @@ default Mono exists(ByteBuffer key) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: TYPE
+ * @see Redis Documentation: TYPE
*/
default Mono type(ByteBuffer key) {
@@ -85,7 +85,7 @@ default Mono type(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: TYPE
+ * @see Redis Documentation: TYPE
*/
Flux> type(Publisher keys);
@@ -94,7 +94,7 @@ default Mono type(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return {@link Mono} emitting the number of keys touched.
- * @see Redis Documentation: TOUCH
+ * @see Redis Documentation: TOUCH
* @since 2.1
*/
default Mono touch(Collection keys) {
@@ -106,7 +106,7 @@ default Mono touch(Collection keys) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: TOUCH
+ * @see Redis Documentation: TOUCH
* @since 2.1
*/
Flux, Long>> touch(Publisher> keys);
@@ -118,7 +118,7 @@ default Mono touch(Collection keys) {
*
* @param pattern must not be {@literal null}.
* @return
- * @see Redis Documentation: KEYS
+ * @see Redis Documentation: KEYS
*/
default Mono> keys(ByteBuffer pattern) {
@@ -134,7 +134,7 @@ default Mono> keys(ByteBuffer pattern) {
*
* @param patterns must not be {@literal null}.
* @return
- * @see Redis Documentation: KEYS
+ * @see Redis Documentation: KEYS
*/
Flux> keys(Publisher patterns);
@@ -143,7 +143,7 @@ default Mono> keys(ByteBuffer pattern) {
* commands itself as long as the subscriber signals demand.
*
* @return never {@literal null}.
- * @see Redis Documentation: SCAN
+ * @see Redis Documentation: SCAN
* @since 2.1
*/
default Flux scan() {
@@ -157,7 +157,7 @@ default Flux scan() {
* @param options must not be {@literal null}.
* @return the {@link Flux} emitting {@link ByteBuffer keys} one by one.
* @throws IllegalArgumentException when options is {@literal null}.
- * @see Redis Documentation: SCAN
+ * @see Redis Documentation: SCAN
* @since 2.1
*/
Flux scan(ScanOptions options);
@@ -166,7 +166,7 @@ default Flux scan() {
* Return a random key from the keyspace.
*
* @return
- * @see Redis Documentation: RANDOMKEY
+ * @see Redis Documentation: RANDOMKEY
*/
Mono randomKey();
@@ -174,7 +174,7 @@ default Flux scan() {
* {@code RENAME} command parameters.
*
* @author Christoph Strobl
- * @see Redis Documentation: RENAME
+ * @see Redis Documentation: RENAME
*/
class RenameCommand extends KeyCommand {
@@ -228,7 +228,7 @@ public ByteBuffer getNewName() {
* @param key must not be {@literal null}.
* @param newName must not be {@literal null}.
* @return
- * @see Redis Documentation: RENAME
+ * @see Redis Documentation: RENAME
*/
default Mono rename(ByteBuffer key, ByteBuffer newName) {
@@ -242,7 +242,7 @@ default Mono rename(ByteBuffer key, ByteBuffer newName) {
*
* @param command must not be {@literal null}.
* @return
- * @see Redis Documentation: RENAME
+ * @see Redis Documentation: RENAME
*/
Flux> rename(Publisher command);
@@ -252,7 +252,7 @@ default Mono rename(ByteBuffer key, ByteBuffer newName) {
* @param key must not be {@literal null}.
* @param newName must not be {@literal null}.
* @return
- * @see Redis Documentation: RENAMENX
+ * @see Redis Documentation: RENAMENX
*/
default Mono renameNX(ByteBuffer key, ByteBuffer newName) {
@@ -266,7 +266,7 @@ default Mono renameNX(ByteBuffer key, ByteBuffer newName) {
*
* @param command must not be {@literal null}.
* @return
- * @see Redis Documentation: RENAMENX
+ * @see Redis Documentation: RENAMENX
*/
Flux> renameNX(Publisher command);
@@ -275,7 +275,7 @@ default Mono renameNX(ByteBuffer key, ByteBuffer newName) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: DEL
+ * @see Redis Documentation: DEL
*/
default Mono del(ByteBuffer key) {
@@ -289,7 +289,7 @@ default Mono del(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return {@link Flux} of {@link NumericResponse} holding the {@literal key} removed along with the deletion result.
- * @see Redis Documentation: DEL
+ * @see Redis Documentation: DEL
*/
Flux> del(Publisher keys);
@@ -298,7 +298,7 @@ default Mono del(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: DEL
+ * @see Redis Documentation: DEL
*/
default Mono mDel(List keys) {
@@ -312,7 +312,7 @@ default Mono mDel(List keys) {
*
* @param keys must not be {@literal null}.
* @return {@link Flux} of {@link NumericResponse} holding the {@literal keys} removed along with the deletion result.
- * @see Redis Documentation: DEL
+ * @see Redis Documentation: DEL
*/
Flux, Long>> mDel(Publisher> keys);
@@ -322,7 +322,7 @@ default Mono mDel(List keys) {
*
* @param key must not be {@literal null}.
* @return
- * @see Redis Documentation: UNLINK
+ * @see Redis Documentation: UNLINK
* @since 2.1
*/
default Mono unlink(ByteBuffer key) {
@@ -338,7 +338,7 @@ default Mono unlink(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return {@link Flux} of {@link NumericResponse} holding the {@literal key} removed along with the unlink result.
- * @see Redis Documentation: UNLINK
+ * @see Redis Documentation: UNLINK
* @since 2.1
*/
Flux> unlink(Publisher keys);
@@ -349,7 +349,7 @@ default Mono unlink(ByteBuffer key) {
*
* @param keys must not be {@literal null}.
* @return
- * @see Redis Documentation: UNLINK
+ * @see Redis Documentation: UNLINK
* @since 2.1
*/
default Mono mUnlink(List keys) {
@@ -365,7 +365,7 @@ default Mono mUnlink(List keys) {
*
* @param keys must not be {@literal null}.
* @return {@link Flux} of {@link NumericResponse} holding the {@literal key} removed along with the deletion result.
- * @see Redis Documentation: UNLINK
+ * @see Redis Documentation: UNLINK
* @since 2.1
*/
Flux, Long>> mUnlink(Publisher> keys);
@@ -374,8 +374,8 @@ default Mono mUnlink(List keys) {
* {@code EXPIRE}/{@code PEXPIRE} command parameters.
*
* @author Mark Paluch
- * @see Redis Documentation: EXPIRE
- * @see Redis Documentation: PEXPIRE
+ * @see Redis Documentation: EXPIRE
+ * @see Redis Documentation: PEXPIRE
*/
class ExpireCommand extends KeyCommand {
@@ -429,7 +429,7 @@ public Duration getTimeout() {
* @param key must not be {@literal null}.
* @param timeout must not be {@literal null}.
* @return
- * @see Redis Documentation: EXPIRE
+ * @see Redis Documentation: EXPIRE
*/
default Mono expire(ByteBuffer key, Duration timeout) {
@@ -445,7 +445,7 @@ default Mono expire(ByteBuffer key, Duration timeout) {
* @param commands must not be {@literal null}.
* @return {@link Flux} of {@link BooleanResponse} holding the {@literal key} removed along with the expiration
* result.
- * @see Redis Documentation: EXPIRE
+ * @see Redis Documentation: EXPIRE
*/
Flux> expire(Publisher commands);
@@ -455,7 +455,7 @@ default Mono expire(ByteBuffer key, Duration timeout) {
* @param key must not be {@literal null}.
* @param timeout must not be {@literal null}.
* @return
- * @see Redis Documentation: PEXPIRE
+ * @see Redis Documentation: PEXPIRE
*/
default Mono pExpire(ByteBuffer key, Duration timeout) {
@@ -471,7 +471,7 @@ default Mono pExpire(ByteBuffer key, Duration timeout) {
* @param commands must not be {@literal null}.
* @return {@link Flux} of {@link BooleanResponse} holding the {@literal key} removed along with the expiration
* result.
- * @see Redis Documentation: PEXPIRE
+ * @see Redis Documentation: PEXPIRE
*/
Flux> pExpire(Publisher commands);
@@ -479,8 +479,8 @@ default Mono pExpire(ByteBuffer key, Duration timeout) {
* {@code EXPIREAT}/{@code PEXPIREAT} command parameters.
*
* @author Mark Paluch
- * @see Redis Documentation: EXPIREAT
- * @see Redis Documentation: PEXPIREAT
+ * @see Redis Documentation: EXPIREAT
+ * @see Redis Documentation: PEXPIREAT
*/
class ExpireAtCommand extends KeyCommand {
@@ -534,7 +534,7 @@ public Instant getExpireAt() {
* @param key must not be {@literal null}.
* @param expireAt must not be {@literal null}.
* @return
- * @see Redis Documentation: EXPIREAT
+ * @see Redis Documentation: EXPIREAT
*/
default Mono expireAt(ByteBuffer key, Instant expireAt) {
@@ -550,7 +550,7 @@ default Mono expireAt(ByteBuffer key, Instant expireAt) {
* @param commands must not be {@literal null}.
* @return {@link Flux} of {@link BooleanResponse} holding the {@literal key} removed along with the expiration
* result.
- * @see Redis Documentation: EXPIREAT
+ * @see Redis Documentation: EXPIREAT
*/
Flux> expireAt(Publisher commands);
@@ -560,7 +560,7 @@ default Mono expireAt(ByteBuffer key, Instant expireAt) {
* @param key must not be {@literal null}.
* @param expireAt must not be {@literal null}.
* @return
- * @see Redis Documentation: PEXPIREAT
+ * @see Redis Documentation: PEXPIREAT
*/
default Mono pExpireAt(ByteBuffer key, Instant expireAt) {
@@ -576,7 +576,7 @@ default Mono