-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
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
dynamodbattribute.Marshal() does not marshal json.Number to Numeric data type #3643
Comments
Hi @MartinGall-Emis , |
so, I've got an update on this. Good news is, this will be something we work on. I'll be opening an issue to track this on the V2 issue queue. Feel free to comment on it if I missed something or if you want to add to the description. |
@KaibaLopez Thank you so much for the update 👍 For the time being we can continue to work around this by using dynamodbattribute.ConvertTo(...) where required until the issue in aws-sdk-go-v2 is progressed. |
This issue has been fixed in https://github.com/aws/aws-sdk-go-v2, please use the v2 sdk . |
|
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
The deprecated
dynamodbattribute.ConvertTo(...)
function converts any values of the json.Number type to the numeric dynamodb data typeN:
When migrating to the replacement
dynamdbattribute.Marshal(...)
the same numeric value is converted to the string dynamodb data type 'S:' instead of 'N:'Version of AWS SDK for Go?
v1.35.20
aws.SDKVersion
in your code after importing"github.com/aws/aws-sdk-go/aws"
Version of Go (
go version
)?1.15.2
To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code or minimal repo)
Expected behavior
I would expect dynamodbattribute.Marshal(...) to marshal values with a type of json.Number to N: as per the dynamodbattribute.ConvertTo(...) implementation i.e.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: