Error: dynamodb does not accept empty set
What's Causing This Error
This used to be an error that occurred before 20th May 2020. However, if you are running into this error in 2022, it is most likely that you are running on an old SDK version, or you have not enabled empty value conversion in the Document Client.
Solution: Here's How To Resolve It
Firstly, upgrade your AWS SDK to the latest version.
npm i aws-sdk@latest
Hereafter, set the convertEmptyValues
property to true when initializing an instance of Document Client, as shown below.
const aws = require('aws-sdk'); const documentClient = new aws.sdk.DynamoDb.DocumentClient({ convertEmptyValues: true });
Other Common DynamoDB Errors (with Solutions)
- DynamoDB stream no records processed
- dynamodb query is null
- dynamodb the table does not have the specified index
- dynamodb-admin is not recognized as an internal or external command
- dynamodb consistent reads are not supported on global secondary indexes
- dynamodb table did not stabilize
- dynamodb query is not null
- dynamodb text contents could not be decoded
- dynamodb net scan condition or not working
- dynamodb exclusivestartkey not working
- dynamodb connection timeout
- sls dynamodb install not working
- dynamodb put item not working
- dynamodb global secondary index does not project
- amazon dynamodb query parentparams is not defined
Dynobase is a Professional GUI Client for DynamoDB
First 7 days are on us. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2023 Dynobase