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
Well, I'm not sure this would work even if you marked your property with just one of those attributes.
Linq2DynamoDB doesn't require and doesn't support neither DynamoDBHashKey nor DynamoDBGlobalSecondaryIndexHashKey.
I had a table where one attribute was the table hash key as well as the hash key for a global secondary index. I tried commenting out the DynamoDBGlobalSecondaryIndexHashKey attribute, and instead got some other error (which I didn't note at the time, sorry, but I think it had do with DynamoDB not able to tell if I was querying using the primary key or the GSI). In the end, it turned out I didn't need that GSI, so we just dropped it, completely side-stepping this issue.
Still, you could fix the bug by finding the first DynamoDBAttribute that has a converter defined, since it doesn't make sense that a column would require two different converters.
If a property is part of the primary key and also an index, there's an exception thrown when trying to determine the property converter.
Example:
The error is in DynamoDbConversionUtils.GetPropertyConverter():
The text was updated successfully, but these errors were encountered: