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

Fix a bad link in the fluentd doc #5195

Merged
merged 1 commit into from
Jul 25, 2024
Merged

Fix a bad link in the fluentd doc #5195

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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/integrations/fluentd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -357,7 +357,7 @@ degrade as many small commits accumulate. However, the `-manage 5m` option
that was included when starting our Zed lake service mitigates this effect
by compacting the data in the lake's pools every five minutes. This results
in storing the pool data across a smaller number of larger
[data objects](../commands/zed.md#data), allowing for better query performance
[data objects](../lake/format.md#data-objects), allowing for better query performance
as data volumes increase.

By default, even after compaction is performed, the granular commit history is
Expand Down