This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/master by this push:
new 92dafdfc0e82 [MINOR][DOC] Fix missing subject in event log compaction
note
92dafdfc0e82 is described below
commit 92dafdfc0e82e6d95dea3a8b8933508bc42ddbea
Author: Tamir Krasna <[email protected]>
AuthorDate: Wed Oct 28 17:18:02 2026 -0700
[MINOR][DOC] Fix missing subject in event log compaction note
### What changes were proposed in this pull request?
This PR fixes an ungrammatical sentence in `docs/monitoring.md`. The clause
`if figures out not a lot of space would be reduced during compaction` is
missing its subject.
Before:
> ... may not compact the old event log files if figures out not a lot of
> space would be reduced during compaction.
After:
> ... may not compact the old event log files if it determines that
> compaction would not reclaim much space.
### Why are the changes needed?
The sentence is grammatically incomplete and hard to parse. "Space would be
reduced" is also the wrong sense — compaction reclaims space rather than
reducing it.
### Does this PR introduce _any_ user-facing change?
No. Documentation only.
### How was this patch tested?
N/A. Documentation change only.
### Was this patch authored or co-authored using generative AI tooling?
No.
Closes #57873 from Tankdoggo/minor-docs-compaction-typo.
Lead-authored-by: Tamir Krasna <[email protected]>
Co-authored-by: Your Name <tamirkrasna@my_email.comm>
Signed-off-by: Holden Karau <[email protected]>
---
docs/monitoring.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/monitoring.md b/docs/monitoring.md
index ded2e48ae2f7..05a0515aa5d7 100644
--- a/docs/monitoring.md
+++ b/docs/monitoring.md
@@ -137,7 +137,7 @@ a new event log file is rolled.
Once rewriting is done, original log files will be deleted, via best-effort
manner. The History Server may not be able to delete
the original log files, but it will not affect the operation of the History
Server.
-Please note that Spark History Server may not compact the old event log files
if figures out not a lot of space
+Please note that Spark History Server may not compact the old event log files
if it figures out that not a lot of space
would be reduced during compaction. For streaming query we normally expect
compaction
will run as each micro-batch will trigger one or more jobs which will be
finished shortly, but compaction won't run
in many cases for batch query.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
