-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
docs: Update docs for structured metadata blooms #14555
docs: Update docs for structured metadata blooms #14555
Conversation
The bloom compactor component has been removed in favor of the bloom planner/builder/gateway, none of which use hash rings.
Replace references to bloom compactor with the new bloom planner and bloom builder components.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏 LGTM
Update the Query Acceleration with Blooms topic to reference structured metadata blooms over the removed line blooms. Documentation on how to configure bloom components has been temporarily removed while the architecture is still under active changes.
6c94ad6
to
0117f2b
Compare
a8acc16
to
4561c6f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team]
Co-authored-by: J Stickler <julie.stickler@grafana.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[docs team] Just a few small tweaks, but otherwise LGTM. Moving the query section should really improve findability for that information. And I like that you linked to the section from the main bloom filters topic. 👍
Co-authored-by: J Stickler <julie.stickler@grafana.com>
Oh, one last thing, do we need to backport this to any of the branches, for example does this need to be published to 3.2? Or is this just going into the "next" release? |
Good question, I'm pretty sure that all of our bloom changes weren't backported to 3.2, so I think keeping this in next is the right move. cc @salvacorts @chaudum for final confirmation (I'll backport after merging if necessary) |
cbb8bc8
to
83d7929
Compare
What this PR does / why we need it:
Documentation for how to configure the new bloom components has been temporarily removed as we are still actively making changes to the architecture.
Which issue(s) this PR fixes:
Closes #14414
Special notes for your reviewer:
Checklist
CONTRIBUTING.md
guide (required)feat
PRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.md
deprecated-config.yaml
anddeleted-config.yaml
files respectively in thetools/deprecated-config-checker
directory. Example PR