Skip to content

Added ProgressThrottler#70

Open
MFormenti wants to merge 2 commits intomainfrom
add-progress-throttler
Open

Added ProgressThrottler#70
MFormenti wants to merge 2 commits intomainfrom
add-progress-throttler

Conversation

@MFormenti
Copy link
Copy Markdown

Added ProgressThrottler, a generic throttler for progress updates during scans. Ensures updates are published at most once per configurable time window

Added unit tests and integration tests for ProgressThrottler
Copy link
Copy Markdown
Contributor

@juaninf juaninf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems ProgressThrottler is added as a standalone utility class but it is not integrated into BulkScanWorker, which seems is the natural way where it should be. BulkScanWorker already has the progressConsumer pipeline in handle(). Putting it with the throttler here would make throttled partial result persistence a built-in framework feature rather than something each subclass has to wire up manually.

@MFormenti
Copy link
Copy Markdown
Author

ProgressThrottler is now integrated into BulkScanWorker.handle(), which wraps the progressConsumer with throttling before passing it to scan().

Throttled partial result publishing is now a built-in framework feature
BulkScanWorker.handle() wraps the progressConsumer transparently.
Config (partialResultsEnabled, partialResultThrottleMs) added to ScanConfig.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants