We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For events that receive records in array format, such as Kinesis/SQS, you may want to PUT the results of each event into DynamoDB.
In these cases, BatchWriter is used to write to the event, and it is more convenient in some cases to handle the records as they are.
jeffy.handlers.sqs
jeffy.handlers.sqs_each
or
jeffy.handlers.sqs_batch
jeffy.handlers.sqs_records
As mentioned above, how about providing handlers that can be received both arrays/each element?
Related discussion: serverless-operations/jeffy-ja#1
The text was updated successfully, but these errors were encountered:
@hassaku63 Thank you for the suggestion 👍 I agree with your idea.
Add a decorator argument that tells the lambda handler receives an event object single record or arrayed records
I personally prefer this option since we should keep the compatibility of Jeffy's previous versions.
Sorry, something went wrong.
No branches or pull requests
For events that receive records in array format, such as Kinesis/SQS, you may want to PUT the results of each event into DynamoDB.
In these cases, BatchWriter is used to write to the event, and it is more convenient in some cases to handle the records as they are.
jeffy.handlers.sqs
to another (e.gjeffy.handlers.sqs_each
)jeffy.handlers.sqs
as the handler receives records as an arrayor
jeffy.handlers.sqs_batch
/jeffy.handlers.sqs_records
)or
As mentioned above, how about providing handlers that can be received both arrays/each element?
Related discussion: serverless-operations/jeffy-ja#1
The text was updated successfully, but these errors were encountered: