From 04a91f961e3d7641f25914be4c9f3c5e3c1e1e8f Mon Sep 17 00:00:00 2001
From: Duo Zhang <zhangduo@apache.org>
Date: Wed, 12 Jun 2019 10:50:44 +0800
Subject: [PATCH] HBASE-22569 Should treat null consistency as
 Consistency.STRONG in ConnectionUtils.timelineConsistentRead

---
 .../java/org/apache/hadoop/hbase/client/ConnectionUtils.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionUtils.java b/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionUtils.java
index 4a2fa3a9b55..cad0c65516d 100644
--- a/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionUtils.java
+++ b/hbase-client/src/main/java/org/apache/hadoop/hbase/client/ConnectionUtils.java
@@ -545,7 +545,7 @@ public final class ConnectionUtils {
       TableName tableName, Query query, byte[] row, RegionLocateType locateType,
       Function<Integer, CompletableFuture<T>> requestReplica, long rpcTimeoutNs,
       long primaryCallTimeoutNs, Timer retryTimer, Optional<MetricsConnection> metrics) {
-    if (query.getConsistency() == Consistency.STRONG) {
+    if (query.getConsistency() != Consistency.TIMELINE) {
       return requestReplica.apply(RegionReplicaUtil.DEFAULT_REPLICA_ID);
     }
     // user specifies a replica id explicitly, just send request to the specific replica