Querying a Global Secondary Index in dynamodb Local

38,847

Solution 1

Try to change ExpressionAttributeValues from this

{ 
 TableName: 'Configs',
 IndexName: 'publisher_index',
 KeyConditionExpression: 'publisherId = :pub_id',
 ExpressionAttributeValues: { ':pub_id': { S: '700' } } 
}

to

{ 
 TableName: 'Configs',
 IndexName: 'publisher_index',
 KeyConditionExpression: 'publisherId = :pub_id',
 ExpressionAttributeValues: { ':pub_id': '700'} 
}

From { ':pub_id': { S: '700' } } to { ':pub_id': '700'}.

I had the same problem and I spent 2 days for this. The official documentation in misleading.

Solution 2

Turns out it depends on whether you use AWS.DynamoDB or AWS.DynamoDB.DocumentClient.

Check the difference in the documentation: AWS.DynamoDB.query vs. AWS.DynamoDB.DocumentClient.query

In the DocumentClient the doc clearly states:

The document client simplifies working with items in Amazon DynamoDB by abstracting away the notion of attribute values. This abstraction annotates native JavaScript types supplied as input parameters, as well as converts annotated response data to native JavaScript types.

...

Supply the same parameters as AWS.DynamoDB.query() with AttributeValues substituted by native JavaScript types.

Maybe you where also referring to the DynamoDB API Reference which in fact makes no assumptions about the used SDK but uses plain HTTP Requests in the examples.

Thus using the AWS.DynamoDB.DocumentClient you would just provide a simple key-value map for ExpressionAttributeValues as suggested by @gior91.

Solution 3

As stated above, you need to use the DynamoDB Document Client if you want to abtract away the type casting.

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

...then you can just use the above listed object notation to call the API.

{ ':pub_id': '700'}

Ran into this issue myself, I was using DynamoDB() in some places and the docClient in others, couldn't figure it out for awhile, but that'll solve it.

Solution 4

I found the other answers very helpful, but I still couldn't get the ValidationExceptions to go away... eventually I realized that I'd been using the DocumentClient's .get instead of .query 🤦

(Technically not an answer to the question, but posting this here rather than in a comment to make it more visible to anyone else struggling with such a marvellously unhelpful error message.)

Share:
38,847
Stelios Savva
Author by

Stelios Savva

Updated on June 14, 2021

Comments

  • Stelios Savva
    Stelios Savva almost 3 years

    I am creating a table and GSI in DynamoDB, using these parameters, as per the documentation:

    configId is the primary key of the table, and I am using the publisherId as the primary key for the GSI. (I've removed some unnecessary configuration parameters for brevity)

    var params = {
        TableName: 'Configs',
        KeySchema: [ 
            {
                AttributeName: 'configId',
                KeyType: 'HASH',
            }
        ],
        AttributeDefinitions: [
            {
                AttributeName: 'configId',
                AttributeType: 'S',
            },
            {
                AttributeName: 'publisherId',
                AttributeType: 'S',
            }
        ],
        GlobalSecondaryIndexes: [ 
            { 
                IndexName: 'publisher_index', 
                KeySchema: [
                    {
                        AttributeName: 'publisherId',
                        KeyType: 'HASH',
                    }
                ]
            }
        ]
    };
    

    I am querying this table using this:

    { TableName: 'Configs',
      IndexName: 'publisher_index',
      KeyConditionExpression: 'publisherId = :pub_id',
      ExpressionAttributeValues: { ':pub_id': { S: '700' } } }
    

    but I keep getting the error:

    "ValidationException: One or more parameter values were invalid: Condition parameter type does not match schema type"

    In the docs it specifies that the primary KeyType can either be HASH or RANGE, and that you set the AttributeType in the AttributeDefinitions field. I am sending the publisherId as String, not sure what I am missing here.

    Is the issue in the way I am creating the table, or the way I am querying? Thanks

  • Hatim Khouzaimi
    Hatim Khouzaimi about 8 years
    Sorry, I tried this but it does not work for me. When I do not provide something with the datatype, like in: { ':pub_id': { S: '700' } }, I get a validation error. Are you sure you are not talking about ExpressionAttributesNames instead of ExpressionAttributesValues?
  • gior91
    gior91 about 8 years
    The correct keyword is ExpressionAttributeValues and not AttributeS. Are you sure that your ValidationException is not dued to this little mistake? In my case I don't used the ExpressionAttributeNames parameter and that worked.
  • ckuijjer
    ckuijjer almost 8 years
    @gior91 Cool! This really helped me. Thanks!
  • gior91
    gior91 about 5 years
    @RobertOschler you're welcome! I'm surprised that after ~3 years this error is still present!!!
  • Robert Oschler
    Robert Oschler about 5 years
    @gior91 Sign of the times. Seeing the same thing in blockchain. The platforms change so fast, the docs can't keep up or worse, there's multiple sets for multiple version, but the old docs naturally rise to the top of the search engines over the new ones due to their larger more mature link networks.
  • Jack Ryan
    Jack Ryan over 3 years
    This is because when you use the DocumentClient, you no longer need the "S" to indicate that it's a string. Under the hood the API takes that data, but the DocumentClient abstracts it away from you in Node. docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB/…
  • AirOne
    AirOne about 2 years
    Well you actually helped me there, that was the origin of my error. Thanks !