From c45e2968f685ce9f2348816e561a61f489712ff1 Mon Sep 17 00:00:00 2001 From: J Stickler Date: Wed, 27 Nov 2024 16:49:55 -0500 Subject: [PATCH] docs: Update query-acceleration-blooms.md (#14544) (#15168) Co-authored-by: pmo --- 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 a5076d1b7d99..74e8ed29c62f 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.