SerializationException when making Gettem request to DynamoDB via API Gateway











up vote
0
down vote

favorite
1












I'm making a GetItem call to a DynamoDB via API Gateway integration. My request mapping is:



{
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "$input.params('entity-id')"}
}
}
}



Response template is:
{ "payload" : "$input.json('$')"}



Logs that I get:



Thu Nov 22 10:31:51 UTC 2018 : Endpoint request body after transformations: {
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "123"}
}
}
}



Thu Nov 22 10:31:51 UTC 2018 : Sending request to https://dynamodb.eu-west-1.amazonaws.com/?Action=GetItem
Thu Nov 22 10:31:51 UTC 2018 : Method response body after transformations: {"__type":"com.amazon.coral.service#SerializationException"}
Thu Nov 22 10:31:51 UTC 2018 : Method response headers: {X-Amzn-Trace-Id=Root=1-5bf68597-8d22f7ca52c6af2aded083e0, Content-Type=application/json}
Thu Nov 22 10:31:51 UTC 2018 : Successfully completed execution
Thu Nov 22 10:31:51 UTC 2018 : Method completed with status: 404



Any ideas whats wrong? Or how to debug it?










share|improve this question






















  • This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
    – Matthew Pope
    Nov 22 at 17:35












  • Did you ever find a solution to this problem?
    – Matthew Pope
    Dec 10 at 23:53










  • Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
    – sumek
    Dec 11 at 12:23

















up vote
0
down vote

favorite
1












I'm making a GetItem call to a DynamoDB via API Gateway integration. My request mapping is:



{
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "$input.params('entity-id')"}
}
}
}



Response template is:
{ "payload" : "$input.json('$')"}



Logs that I get:



Thu Nov 22 10:31:51 UTC 2018 : Endpoint request body after transformations: {
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "123"}
}
}
}



Thu Nov 22 10:31:51 UTC 2018 : Sending request to https://dynamodb.eu-west-1.amazonaws.com/?Action=GetItem
Thu Nov 22 10:31:51 UTC 2018 : Method response body after transformations: {"__type":"com.amazon.coral.service#SerializationException"}
Thu Nov 22 10:31:51 UTC 2018 : Method response headers: {X-Amzn-Trace-Id=Root=1-5bf68597-8d22f7ca52c6af2aded083e0, Content-Type=application/json}
Thu Nov 22 10:31:51 UTC 2018 : Successfully completed execution
Thu Nov 22 10:31:51 UTC 2018 : Method completed with status: 404



Any ideas whats wrong? Or how to debug it?










share|improve this question






















  • This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
    – Matthew Pope
    Nov 22 at 17:35












  • Did you ever find a solution to this problem?
    – Matthew Pope
    Dec 10 at 23:53










  • Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
    – sumek
    Dec 11 at 12:23















up vote
0
down vote

favorite
1









up vote
0
down vote

favorite
1






1





I'm making a GetItem call to a DynamoDB via API Gateway integration. My request mapping is:



{
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "$input.params('entity-id')"}
}
}
}



Response template is:
{ "payload" : "$input.json('$')"}



Logs that I get:



Thu Nov 22 10:31:51 UTC 2018 : Endpoint request body after transformations: {
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "123"}
}
}
}



Thu Nov 22 10:31:51 UTC 2018 : Sending request to https://dynamodb.eu-west-1.amazonaws.com/?Action=GetItem
Thu Nov 22 10:31:51 UTC 2018 : Method response body after transformations: {"__type":"com.amazon.coral.service#SerializationException"}
Thu Nov 22 10:31:51 UTC 2018 : Method response headers: {X-Amzn-Trace-Id=Root=1-5bf68597-8d22f7ca52c6af2aded083e0, Content-Type=application/json}
Thu Nov 22 10:31:51 UTC 2018 : Successfully completed execution
Thu Nov 22 10:31:51 UTC 2018 : Method completed with status: 404



Any ideas whats wrong? Or how to debug it?










share|improve this question













I'm making a GetItem call to a DynamoDB via API Gateway integration. My request mapping is:



{
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "$input.params('entity-id')"}
}
}
}



Response template is:
{ "payload" : "$input.json('$')"}



Logs that I get:



Thu Nov 22 10:31:51 UTC 2018 : Endpoint request body after transformations: {
"TableName": "connected-content-dynamodb",
"Key": {
{ "id" :
{"S" : "123"}
}
}
}



Thu Nov 22 10:31:51 UTC 2018 : Sending request to https://dynamodb.eu-west-1.amazonaws.com/?Action=GetItem
Thu Nov 22 10:31:51 UTC 2018 : Method response body after transformations: {"__type":"com.amazon.coral.service#SerializationException"}
Thu Nov 22 10:31:51 UTC 2018 : Method response headers: {X-Amzn-Trace-Id=Root=1-5bf68597-8d22f7ca52c6af2aded083e0, Content-Type=application/json}
Thu Nov 22 10:31:51 UTC 2018 : Successfully completed execution
Thu Nov 22 10:31:51 UTC 2018 : Method completed with status: 404



Any ideas whats wrong? Or how to debug it?







amazon-web-services amazon-dynamodb aws-api-gateway api-gateway






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 11:21









sumek

10.7k94254




10.7k94254












  • This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
    – Matthew Pope
    Nov 22 at 17:35












  • Did you ever find a solution to this problem?
    – Matthew Pope
    Dec 10 at 23:53










  • Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
    – sumek
    Dec 11 at 12:23




















  • This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
    – Matthew Pope
    Nov 22 at 17:35












  • Did you ever find a solution to this problem?
    – Matthew Pope
    Dec 10 at 23:53










  • Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
    – sumek
    Dec 11 at 12:23


















This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
– Matthew Pope
Nov 22 at 17:35






This is entirely speculation, but it looks like you have extra { and } in your request json. Maybe that’s the problem. It definitely possible that it could cause a com.amazon.coral.SerializationException.
– Matthew Pope
Nov 22 at 17:35














Did you ever find a solution to this problem?
– Matthew Pope
Dec 10 at 23:53




Did you ever find a solution to this problem?
– Matthew Pope
Dec 10 at 23:53












Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
– sumek
Dec 11 at 12:23






Sadly no. we've stuck to using Query for now. It works except we always get 200 response code even when there is no result. But tbh only discovered logging afterwards.
– sumek
Dec 11 at 12:23



















active

oldest

votes











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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429848%2fserializationexception-when-making-gettem-request-to-dynamodb-via-api-gateway%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53429848%2fserializationexception-when-making-gettem-request-to-dynamodb-via-api-gateway%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Contact image not getting when fetch all contact list from iPhone by CNContact

count number of partitions of a set with n elements into k subsets

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks