-
Notifications
You must be signed in to change notification settings - Fork 859
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
DynamoDB dynamodb:DescribeTable Error when using OverrideTableName #1421
Comments
Hi @Artin-ST, thanks for reporting this. I think it is root caused by a known bug. I'll look into this more soon and add more details as I go along. |
Hello, any update on this bug ? I can still reproduce this exact same issue with AWSSDK.DynamoDBv2 version 3.3.105.26 on .NET Core 3.1 Project. |
Hey there, in the exact same manner as the OP I found out that I suffer from this bug as well. Considering that the OPM is used quite generally around here , this issue is definitely pretty widespread. |
Breaking change as per #1218 (comment) |
Also refer #1448 and validate the scenario if this issue is fixed in next major release. |
We have noticed this issue has not received attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue. |
@ashishdhingra Both this one and #1448 are closed now. Could you please reopen one of them to make sure the error is tracked? |
In our next major version of the SDK (development underway now, see #3209), we've separated the hierarchy between var dynamoDbOperationConfig = new DynamoDBOperationConfig
{
OverrideTableName = _tableName
};
var context = new DynamoDBContext(_client, dynamoDbOperationConfig); // no longer possible in V4 We didn't want to take a single override table name as an input to the context object, since one can reuse a context object with multiple tables. If you do want to override table names on an application-level, you can use the We'll close this once V4 packages ship with this change. This addresses #1218 which we de-duped into this one. Revisiting this issue and #1448 which was also de-duped here. These appear to be both be overriding the table name via a var config = new DynamoDBOperationConfig
{
OverrideTableName = “TableName”,
};
var query = context.QueryAsync<ObjectType>(“HashKey”, config); |
Hello @ayongbannayan, These changes are available in .NET 4 Preview. Kindly track this issue for when this change would go GA. Will go ahead and close this out. Thank you. Regards, |
Comments on closed issues are hard for our team to see. |
I'm using the object persistent model, the name of the DynamoDB table is also dynamic. My queries currently function however when using X-Ray I'm noticing an exception that is occurring after the query.
In my object I am not using the DynamoDBTable attribute because the table name is dynamic. I'm using the DynamoDBOperationConfig and setting the OverrideTableName property.
When excuting QueryAsync the query returns results but X-Ray shows the following
The error that is occurring is ...not authorized to perform: dynamodb:DescribeTable on resource: arn:aws:dynamodb:ca-central-1:xxxxxxxxx:table/T where T is the name of the object and not the table.
I'm not sure how to handle this exception. I've tried to set the DynamoDBTable however the error simply changes to the name I provide instead of the objects Name. Not sure what else I'm missing.
Regards
Artin
The text was updated successfully, but these errors were encountered: