Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Update query-acceleration-blooms.md (#14544) #15168

Merged
merged 2 commits into from
Nov 27, 2024
Merged

docs: Update query-acceleration-blooms.md (#14544) #15168

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
73db8e8
docs: Update query-acceleration-blooms.md (#14544)
pbmoses Nov 27, 2024
928b882
Merge branch 'release-3.1.x' into backport-14544-to-release-3.1.x
JStickler Nov 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/sources/operations/query-acceleration-blooms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading