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
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
I'm using this crate in a Lambda that processes DynamoDB stream events coming from Kinesis.
I can't deserialize the events to aws_lambda_events::dynamodb::EventRecord because the eventVersion field is missing from them. The aws_lambda_events::dynamodb::EventRecord struct has the event_version field as being of type String rather than of type Option<String>. I'm not sure if this is a bug or if I'm just using the wrong type.
I've been able to get around this by duplicating the type, changing the type of the field to Option<String>, and deriving serde::Deserialize on it.
Here is the base64 decoding of the problematic EventRecord. Note the lack of eventVersion field.
Can you open a PR updating the type for that field? there are some fields that are not very well documented, so it's hard at times to know which ones are optional and which ones are not.
Hello! Thank you for this wonderful crate!
I'm using this crate in a Lambda that processes DynamoDB stream events coming from Kinesis.
I can't deserialize the events to
aws_lambda_events::dynamodb::EventRecord
because theeventVersion
field is missing from them. Theaws_lambda_events::dynamodb::EventRecord
struct has theevent_version
field as being of typeString
rather than of typeOption<String>
. I'm not sure if this is a bug or if I'm just using the wrong type.I've been able to get around this by duplicating the type, changing the type of the field to
Option<String>
, and derivingserde::Deserialize
on it.Here is the base64 decoding of the problematic
EventRecord
. Note the lack ofeventVersion
field.Here is what the above looks like as the
data
field of alambda_runtime::LambdaEvent<aws_lambda_events::event::kinesis::KinesisEvent>
.The text was updated successfully, but these errors were encountered: