-
Notifications
You must be signed in to change notification settings - Fork 862
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
DisableFetchingTableMetadata leads to InvalidOperationException if PropertyConverter is used #3323
Comments
Recent PR to this area: #3304 |
Hi @smusenok, Thank you for reporting the issue. I am able to reproduce the Team will further investigate this issue and provide a fix, if applicable. Regards, |
Hi @smusenok, In the meantime, if you need to use the
|
Hi @muhammad-othman, |
We shipped AWSSDK.DynamoDBv2 version 3.7.303.16 yesterday, which contained #3327 which will attempt another cast to a valid type for a table or index key in the case where an Let us know if you're still seeing issues (or new issues) on the new version. |
Comments on closed issues are hard for our team to see. |
Describe the bug
Saving and deserializing documents throw exceptions when PropertyConverter is specified in DynamoDBRangeKeyAttribute and DisableFetchingTableMetadata = true.
Expected Behavior
Should not throw any exception.
Current Behavior
DynamoDBContext.SaveAsync throws exception:
DynamoDBContext.FromDocument throws exception:
Reproduction Steps
Possible Solution
No response
Additional Information/Context
Changing DisableFetchingTableMetadata to false makes this code work using AWSSDK.DynamoDBv2 3.7.303.9.
The last known version where this example works properly with DisableFetchingTableMetadata = true is 3.7.302.23.
AWS .NET SDK and/or Package version used
AWSSDK.DynamoDBv2 3.7.303.9
Targeted .NET Platform
.NET 8
Operating System and version
Windows 10, Ubuntu 22.04.4 LTS
The text was updated successfully, but these errors were encountered: