From 73db8e8e90b604b7d1594558da24c93538a1ae95 Mon Sep 17 00:00:00 2001 From: pmo Date: Wed, 27 Nov 2024 01:04:52 -0800 Subject: [PATCH] docs: Update query-acceleration-blooms.md (#14544) (cherry picked from commit 184630f341edee03235cb6f8502d785120d56b3a) --- docs/sources/operations/query-acceleration-blooms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/operations/query-acceleration-blooms.md b/docs/sources/operations/query-acceleration-blooms.md index a5076d1b7d990..74e8ed29c62f0 100644 --- a/docs/sources/operations/query-acceleration-blooms.md +++ b/docs/sources/operations/query-acceleration-blooms.md @@ -36,7 +36,7 @@ and served by the new [Bloom Gateway](#bloom-gateway) component. ## Enable Query Acceleration with Blooms {{< admonition type="warning" >}} Building and querying bloom filters are by design not supported in single binary deployment. -It can be used with Single Scalable deployment (SSD), but it is recommended to +It can be used with Simple Scalable deployment (SSD), but it is recommended to run bloom components only in fully distributed microservice mode. The reason is that bloom filters also come with a relatively high cost for both building and querying the bloom filters that only pays off at large scale deployments.