From b91d9ddf152f0764bac40558236af2b1ba2eb9ee Mon Sep 17 00:00:00 2001
From: chao chang <chang-chao@users.noreply.github.com>
Date: Mon, 11 Nov 2019 16:20:17 +0900
Subject: [PATCH] DATAREDIS-1066 - Add explanation for Jedis usePooling flag.

Original pull request: #494.
---
 .../redis/connection/jedis/JedisClientConfiguration.java   | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/main/java/org/springframework/data/redis/connection/jedis/JedisClientConfiguration.java b/src/main/java/org/springframework/data/redis/connection/jedis/JedisClientConfiguration.java
index 899851c9b..a08bf97c7 100644
--- a/src/main/java/org/springframework/data/redis/connection/jedis/JedisClientConfiguration.java
+++ b/src/main/java/org/springframework/data/redis/connection/jedis/JedisClientConfiguration.java
@@ -79,6 +79,9 @@ public interface JedisClientConfiguration {
 
 	/**
 	 * @return {@literal true} to use connection-pooling.
+	 * <p>
+	 * valid only for single node Redis, and Jedis Sentinel and Cluster will always use connection-pooling regardless of the setting here.
+	 * </p>
 	 */
 	boolean isUsePooling();
 
@@ -149,7 +152,9 @@ public interface JedisClientConfiguration {
 
 		/**
 		 * Enable connection-pooling.
-		 *
+		 * <p>
+		 * Apply only to single node Redis, and Jedis Sentinel and Cluster will always use connection-pooling.
+		 * </p>
 		 * @return {@link JedisPoolingClientConfigurationBuilder}.
 		 */
 		JedisPoolingClientConfigurationBuilder usePooling();