From a16fee5f88efc2ca85e93b4c8d257b8b2ed2cd05 Mon Sep 17 00:00:00 2001 From: Matthew Jaffee Date: Mon, 17 Jan 2022 10:57:01 -0600 Subject: [PATCH] set shardWidth properly in client the shardwidth22 tests were broken client side, but we didn't realize this because we weren't running the client side tests since moving the client code into the main FB repo until recently (woops), and more recently, we'd stopped running the shardwidth22 tests in the move to Gitlab, so when we re-enabled them we finally noticed that they were broken in the client. All this change does is takes the shardWidth value from the core featurebase package instead of using a hardcoded value in the client package. --- client/client.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/client.go b/client/client.go index 211e7c3f7..082a56634 100644 --- a/client/client.go +++ b/client/client.go @@ -36,7 +36,7 @@ import ( const PQLVersion = "1.0" // DefaultShardWidth is used if an index doesn't have it defined. -const DefaultShardWidth = 1 << 20 +const DefaultShardWidth = pilosa.ShardWidth const maxHosts = 10