DynamoDB - Key element does not match the schema

Question

I'm trying to update an Item in my Dynamodb Table +Users+. I have tried many different ways but I always received the same error message:

The provided key element does not match the schema

The creation of an Item works, as well as a query but not the update. When I check on DynamoDB the user is well created:

{
  "email": "[email protected]",
  "password": "123",
  "registration": 1460136902241,
  "verified": false
}

Here is the table information:

Table name: Users
Primary partition key: email (String)
Primary sort key: registration (Number)

Here is the code (called from lambda):

exports.handler = function(event, context)
{
    var AWS = require("aws-sdk");


    var docClient = new AWS.DynamoDB.DocumentClient();

    var params = {
        TableName: "Users",
        Item:{
            email: "[email protected]",
            password: "123",
            verified: false,
            registration: (new Date()).getTime(),
        }
    };

    // Create the user.

    docClient.put(params, function(err, data)
    {
        if (err)
        {
            context.fail("Put failed...");
            return;
        }

        var params = {
            TableName: "Users",
            Key: { email : "[email protected]" },
            AttributeUpdates: {
                verified: {
                    Action: "PUT",
                    Value: true
                }
            }
        };

        // Update the user.
        docClient.update(params, function(err, data)
        {
            if (err)
            {
                console.log(JSON.stringify(err));
                context.fail(JSON.stringify(err));
                return;
            }
            context.succeed("User successfully updated.");
        });


    });

};

Do you have any idea of what could be wrong in my code?

Mark B · Accepted Answer · 2016-04-08 19:09:49Z

145

You are only providing half of your primary key. Your primary key is a combination of the partition key and range key. You need to include the range key in your Key attribute in the update parameters.

answered Apr 8, 2016 at 19:09

Mark B

203k27 gold badges339 silver badges332 bronze badges

Sign up to request clarification or add additional context in comments.

9 Comments

user6178502 Over a year ago

It works, thank you! But is it possible to have only the email address as primary key ?

auhuman Over a year ago

Yes it is possible to have only email address as primary key. docs.aws.amazon.com/amazondynamodb/latest/developerguide/…

Nazeel Over a year ago

Maybe typos in key name, it happened for me

Dmitry Zlykh Over a year ago

If you still want to query by PK only, you have to use 'query', not 'get' method. In this case you can provide KeyConditionExpression: 'PK = xxx' only.

Azamat Abdullaev Over a year ago

I don't have a range key in my table, and I am providing the partition key, but getting this error when I'm calling deleteItem. Are there any other cases that may cause this error?

|

harishanth raveendren · Accepted Answer · 2020-05-12 12:00:40Z

26

For others who have faced the same challenge and the issue is not fixed by above answers, it is always better to double check the data type of the value being updated, in my case the primary key was expecting a Number and I was trying to update with a string. Silly me

answered May 12, 2020 at 12:00

harishanth raveendren

6248 silver badges9 bronze badges

1 Comment

crftr Over a year ago

I also had a silly issue. My table was created with a composite key (i.e. a primary key AND a sort key). When in reality, I only wanted a primary key experience. Lesson learned--plan ahead!

plantbeard · Accepted Answer · 2022-02-21 22:50:05Z

7

My issue was with the Node SDK for deletes, where the documentation says to provide in format:

... {Key: {'id': {S: '123'}}} ...

Which does not appear to work with the aws-sdk ^2.1077.0. This seems to work:

... {Key: {'id': '123'}} ...

answered Feb 21, 2022 at 22:50

plantbeard

3987 silver badges16 bronze badges

2 Comments

Yassine Sedrani Over a year ago

You saved me from another day of debugging thank you!

G. Shand Over a year ago

Same issue here -- thanks! Perhaps worth mentioning this is specifically for the BatchWriteItem api.

Arpit Jain · Accepted Answer · 2023-07-09 05:49:14Z

For the error,

The provided key element does not match the schema

There could be two possible problems here:

You are only providing half of your primary key. For the primary key, you must provide all of the attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key.
Field's value should have a proper data type as per the table. It is always better to double-check the data type of the value being passed. Maybe, you have defined the primary key as a Number and you are passing a string value in the getItem call.

Hope it helps.

Please add more if there could be other possible reasons.

Sergei Russkikh · Accepted Answer · 2020-06-06 20:59:22Z

1

My checklist when facing this issue:

Check that the name and type of your key correspond to what you have in the database.
Use corresponding attributes to make it explicit. E.g. use @DynamoDBHashKey(attributeName = "userId") in Java to indicate the partition key named userId.
Ensure that only one field or getter marked as partition key in your class.

Please, add more if you know in the comments.

answered Jun 6, 2020 at 20:59

Sergei Russkikh

1231 silver badge7 bronze badges

Comments

double-beep · Accepted Answer · 2021-01-05 12:38:14Z

1

I was doing BatchGetItem, then streamed it to BatchWriteItem (Delete). DeleteItem didn't like it got all attributes from the object instead of only partition and sort key.

Gathering all answers:

mismatch in an attribute name
mismatch in attribute type
half key provided
unnecessary additional keys

edited Jan 5, 2021 at 12:38

double-beep

5,66019 gold badges43 silver badges50 bronze badges

answered Jan 5, 2021 at 12:15

nouveu

5801 gold badge8 silver badges11 bronze badges

Comments

abhiSHH · Accepted Answer · 2023-05-30 09:07:20Z

1

assuming you are using "@aws-sdk/client-dynamodb" in NodeJS
if you have both sort key(ex. post_id) and range key(ex. user_id) in your table(ex. UserPostTable), and if you are updating this table with other attribute(for example image_url) then.

you need to specify both sort key and range key as well

  const updateParams = {
TableName: process.env.TABLE_NAME,
Key: {
  post_id: { S: post_id },
  user_id: { S: user_id },
},
UpdateExpression: "SET image_url = :url",
ExpressionAttributeValues: { ":url": { S: image_url } },};const updateCommand = new UpdateItemCommand(updateParams);

answered May 30, 2023 at 9:07

abhiSHH

4597 silver badges9 bronze badges

Collectives™ on Stack Overflow

DynamoDB - Key element does not match the schema

7 Answers 7

9 Comments

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

9 Comments

1 Comment

2 Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related