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
I see that the AWS SDK has its own internal objectMapper with its own configuration, instead of the one micronaut provided.
We have a custom deserializer to handle dynamodb streams events to our lambda, and its working when we test it in unit tests and Micronaut but unfortunately its not used by AWS SDK, with its own object mapper without that configured.
Do you know if its possible to override the AWS SDK internal instance to be the Micronaut objectmapper?
The text was updated successfully, but these errors were encountered:
We have implemented a custom deserializer for the software.amazon.awssdk.services.dynamodb.model.Record class from the AWS SDK that works as expected when read by the injected Objectmapper as shown below:
val record = objectMapper.readValue(serializedRecordString, Record::class.java)
Then we have implemented a Lambda using the class as an input parameter:
Here we are expecting the Lambda runtime to have access to the custom Serde deserializer and deserialize the incoming data into the expected Record-class. However the application errors during parsing when attempting to parse the incoming data from JSON as it does not appear to use the Micronaut objectMapper.
Issue description
I see that the AWS SDK has its own internal objectMapper with its own configuration, instead of the one micronaut provided.
We have a custom deserializer to handle dynamodb streams events to our lambda, and its working when we test it in unit tests and Micronaut but unfortunately its not used by AWS SDK, with its own object mapper without that configured.
Do you know if its possible to override the AWS SDK internal instance to be the Micronaut objectmapper?
The text was updated successfully, but these errors were encountered: