chore: start tasks based on processing batch size in the queue-processing example #220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b2c0d87 to
021b69c
Compare
joozero
approved these changes
Jul 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Start tasks based on processing batch size in the queue-processing example. Changes were implemented on top of #219.
Motivation and Context
In presence of a number of files less or equal than batch size (10) uploaded to the source bucket, the Lambda function was going to start just as many tasks. This is not required as each task is implemented to process files in batches.
This PR implements the intended approach, as confirmed in the documentation for the queue-processing blueprint:
How Has This Been Tested?
examples/*projectspre-commit run -aon my pull request