DynamoDB update a field which has a JSON as value with integer/num-string as keys in python
I am storing an item with the following structure in my dynamodb table.
Item = {"response": [
{
"answers": {
"11-18": 0,
"19-24": 0
}
}
]}
I want to update response[0].answers.11-18 incrementally.
My command was:
table_resource.update_item(
Key={
'id': 123
},
UpdateExpression="set response[0].answers.11-18 = response[0].answers.11-18 + :inc",
ExpressionAttributeValues={":inc": 1},
ReturnValues="UPDATED_NEW",
)
I get the following error.
An error occurred (ValidationException) when calling the UpdateItem operation: Invalid UpdateExpression: Syntax error; token: "11", near: ".11-"
python python-3.x amazon-dynamodb dynamo-local
add a comment |
I am storing an item with the following structure in my dynamodb table.
Item = {"response": [
{
"answers": {
"11-18": 0,
"19-24": 0
}
}
]}
I want to update response[0].answers.11-18 incrementally.
My command was:
table_resource.update_item(
Key={
'id': 123
},
UpdateExpression="set response[0].answers.11-18 = response[0].answers.11-18 + :inc",
ExpressionAttributeValues={":inc": 1},
ReturnValues="UPDATED_NEW",
)
I get the following error.
An error occurred (ValidationException) when calling the UpdateItem operation: Invalid UpdateExpression: Syntax error; token: "11", near: ".11-"
python python-3.x amazon-dynamodb dynamo-local
add a comment |
I am storing an item with the following structure in my dynamodb table.
Item = {"response": [
{
"answers": {
"11-18": 0,
"19-24": 0
}
}
]}
I want to update response[0].answers.11-18 incrementally.
My command was:
table_resource.update_item(
Key={
'id': 123
},
UpdateExpression="set response[0].answers.11-18 = response[0].answers.11-18 + :inc",
ExpressionAttributeValues={":inc": 1},
ReturnValues="UPDATED_NEW",
)
I get the following error.
An error occurred (ValidationException) when calling the UpdateItem operation: Invalid UpdateExpression: Syntax error; token: "11", near: ".11-"
python python-3.x amazon-dynamodb dynamo-local
I am storing an item with the following structure in my dynamodb table.
Item = {"response": [
{
"answers": {
"11-18": 0,
"19-24": 0
}
}
]}
I want to update response[0].answers.11-18 incrementally.
My command was:
table_resource.update_item(
Key={
'id': 123
},
UpdateExpression="set response[0].answers.11-18 = response[0].answers.11-18 + :inc",
ExpressionAttributeValues={":inc": 1},
ReturnValues="UPDATED_NEW",
)
I get the following error.
An error occurred (ValidationException) when calling the UpdateItem operation: Invalid UpdateExpression: Syntax error; token: "11", near: ".11-"
python python-3.x amazon-dynamodb dynamo-local
python python-3.x amazon-dynamodb dynamo-local
asked Nov 20 '18 at 13:14
MehranMehran
238110
238110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Your nested attribute 11-18
begins with a number, so you can’t use it in an update expression.
If an attribute name begins with a number or contains a space, a special character, or a reserved word, then you must use an expression attribute name to replace that attribute's name in the expression.
You can work around this by using placeholder ExpressionAttributeNames.
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393833%2fdynamodb-update-a-field-which-has-a-json-as-value-with-integer-num-string-as-key%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your nested attribute 11-18
begins with a number, so you can’t use it in an update expression.
If an attribute name begins with a number or contains a space, a special character, or a reserved word, then you must use an expression attribute name to replace that attribute's name in the expression.
You can work around this by using placeholder ExpressionAttributeNames.
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
add a comment |
Your nested attribute 11-18
begins with a number, so you can’t use it in an update expression.
If an attribute name begins with a number or contains a space, a special character, or a reserved word, then you must use an expression attribute name to replace that attribute's name in the expression.
You can work around this by using placeholder ExpressionAttributeNames.
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
add a comment |
Your nested attribute 11-18
begins with a number, so you can’t use it in an update expression.
If an attribute name begins with a number or contains a space, a special character, or a reserved word, then you must use an expression attribute name to replace that attribute's name in the expression.
You can work around this by using placeholder ExpressionAttributeNames.
Your nested attribute 11-18
begins with a number, so you can’t use it in an update expression.
If an attribute name begins with a number or contains a space, a special character, or a reserved word, then you must use an expression attribute name to replace that attribute's name in the expression.
You can work around this by using placeholder ExpressionAttributeNames.
answered Nov 21 '18 at 21:01
Matthew PopeMatthew Pope
1,6841712
1,6841712
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
add a comment |
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
Would it create problems if the nested attribute did not begin with a number when I'm using an ExpressionAttributeName?
– Mehran
Nov 22 '18 at 15:20
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
No. You can use safely use ExpressionAttributeNames for any or every attribute.
– Matthew Pope
Nov 22 '18 at 17:25
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53393833%2fdynamodb-update-a-field-which-has-a-json-as-value-with-integer-num-string-as-key%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown