Skip to content
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

Data missing from dynamodb connector when using “simplify” setting #4957

Closed
napter opened this issue Dec 17, 2022 · 1 comment · Fixed by #4959
Closed

Data missing from dynamodb connector when using “simplify” setting #4957

napter opened this issue Dec 17, 2022 · 1 comment · Fixed by #4959

Comments

@napter
Copy link
Contributor

napter commented Dec 17, 2022

When the dynamodb connector is in “simple” mode, columns containing JSON data (datatype “map”) are being set to null. Here is the results of a query with simplify on, note the null value:
image

Here is the output of the exact same query with simplify turned off, note the same field with “M” data (map) now shows data:
image

Here is the workflow:
{ "meta": { "instanceId": "774a1610bb3dee8ad6ccba09f537e24bcd176ae4f9a16da8b8b4ce530d1284a4" }, "nodes": [ { "parameters": { "operation": "getAll", "tableName": "orders", "scan": true, "filterExpression": "#et=:et", "eavUi": { "eavValues": [ { "attribute": ":et", "value": "OrderParent" } ] }, "options": { "projectionExpression": "", "eanUi": { "eanValues": [ { "key": "#et", "value": "_et" } ] } } }, "id": "9a44f16c-f3ab-4744-a181-86f8c6bd92ba", "name": "AWS DynamoDB", "type": "n8n-nodes-base.awsDynamoDb", "typeVersion": 1, "position": [ 140, 300 ], "credentials": { "aws": { "id": "6", "name": "AWS account" } } } ], "connections": {} }

n8n version:
0.207.0 running in Docker

janober pushed a commit that referenced this issue Dec 22, 2022
…4957 (#4959)

* Added 'M' type to decode attribute for dynamodb

* Fixed bug with return all. Headers from the previous iteration were being passed causing an invalid signature error
@janober janober added the Upcoming Release Will be part of the upcoming release label Dec 22, 2022
@janober
Copy link
Member

janober commented Dec 22, 2022

Fix got released with [email protected]

@janober janober removed the Upcoming Release Will be part of the upcoming release label Dec 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants