From bb5418be0021d73148b15affb302721f4e7cf39d Mon Sep 17 00:00:00 2001 From: J Stickler Date: Wed, 27 Nov 2024 16:51:12 -0500 Subject: [PATCH] docs: Update query-acceleration-blooms.md (#14544) (#15169) 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 2fec5f2922705..9ca4705dcfdfb 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.