You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -144,7 +144,7 @@ Processing batches from SQS works in three stages:
144
144
When using [SQS FIFO queues](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/FIFO-queues.html){target="_blank"}, we will stop processing messages after the first failure, and return all failed and unprocessed messages in `batchItemFailures`.
145
145
This helps preserve the ordering of messages in your queue.
1. **Step 1**. Creates a partial failure batch processor for Kinesis Data Streams. See [partial failure mechanics for details](#partial-failure-mechanics)
174
+
1. Creates a partial failure batch processor for Kinesis Data Streams. See [partial failure mechanics for details](#partial-failure-mechanics)
175
175
176
176
=== "Sample response"
177
177
@@ -200,11 +200,11 @@ Processing batches from DynamoDB Streams works in three stages:
1. Any exception works here. See [extending BatchProcessorSync section, if you want to override this behavior.](#extending-batchprocessor)
238
238
239
-
2. Exceptions raised in `record_handler` will propagate to `process_partial_response`. <br/><br/> We catch them and include each failed batch item identifier in the response dictionary (see `Sample response` tab).
239
+
2. Exceptions raised in `recordHandler` will propagate to `process_partial_response`. <br/><br/> We catch them and include each failed batch item identifier in the response dictionary (see `Sample response` tab).
240
240
241
241
=== "Sample response"
242
242
@@ -397,7 +397,7 @@ Use the `BatchProcessor` directly in your function to access a list of all retur
397
397
***When successful**. We will include a tuple with `success`, the result of `recordHandler`, and the batch record
398
398
***When failed**. We will include a tuple with `fail`, exception as a string, and the batch record
@@ -410,7 +410,7 @@ Within your `recordHandler` function, you might need access to the Lambda contex
410
410
411
411
We can automatically inject the [Lambda context](https://docs.aws.amazon.com/lambda/latest/dg/typescript-context.html){target="_blank"} into your `recordHandler` as optional second argument if you register it when using `BatchProcessorSync` or the `processPartialResponseSync` function.
0 commit comments