We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The reserved characters : and # are not "scrubbed" from expression key/value mappers when the QueryConditional calls cleanAttributeName
Example QueryConditional:
aws-sdk-java-v2/services-custom/dynamodb-enhanced/src/main/java/software/amazon/awssdk/enhanced/dynamodb/internal/conditional/EqualToConditional.java
Lines 36 to 37 in 1a1eb6e
cleanAttributeName:
aws-sdk-java-v2/services-custom/dynamodb-enhanced/src/main/java/software/amazon/awssdk/enhanced/dynamodb/internal/EnhancedClientUtils.java
Lines 48 to 60 in 1a1eb6e
Attribute names with : and # characters would be replaced with placeholders, allowing for successful query of table with those attribute names.
The reserved characters are not replaced, resulting in a 400 due to "ExpressionAttributeNames contains invalid key" during query request.
The text was updated successfully, but these errors were encountered:
Thanks for the bug report. Working on a fix.
Sorry, something went wrong.
+
Successfully merging a pull request may close this issue.
Describe the bug
The reserved characters : and # are not "scrubbed" from expression key/value mappers when the QueryConditional calls cleanAttributeName
Example QueryConditional:
aws-sdk-java-v2/services-custom/dynamodb-enhanced/src/main/java/software/amazon/awssdk/enhanced/dynamodb/internal/conditional/EqualToConditional.java
Lines 36 to 37 in 1a1eb6e
cleanAttributeName:
aws-sdk-java-v2/services-custom/dynamodb-enhanced/src/main/java/software/amazon/awssdk/enhanced/dynamodb/internal/EnhancedClientUtils.java
Lines 48 to 60 in 1a1eb6e
Expected Behavior
Attribute names with : and # characters would be replaced with placeholders, allowing for successful query of table with those attribute names.
Current Behavior
The reserved characters are not replaced, resulting in a 400 due to "ExpressionAttributeNames contains invalid key" during query request.
The text was updated successfully, but these errors were encountered: