feat(services): add configurable batch size with file container rotation #189
+1,202
−125
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds configurable batch size support to all push services and implements per-batch file container rotation for UpdateStreamService following Coveo's catalog stream API best practices.
Key Changes
Configurable Batch Size
All services now support custom batch sizes (max: 256MB):
PushService(source, options, maxQueueSize)StreamService(source, options, userAgents, maxQueueSize)UpdateStreamService(source, options, userAgents, maxQueueSize)File Container Rotation (UpdateStreamService)
Each batch now gets its own file container:
This follows the catalog stream API best practices.
Testing
Part 3 of 3 - Split from PR #186
Dependencies: Should merge after #187 and #188