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
A global secondary index lets you query over the entire table, across all partitions. A local secondary index lets you query over a single partition, as specified by the partition key value in the query. Queries on global secondary indexes support eventual consistency only.
Query a Local Secondary IndexYou must specify the index name, the query criteria for the index sort key, and the attributes that you want to return. In this example, the index is AlbumTitleIndex and the index sort key is AlbumTitle . The only attributes returned are those that have been projected into the index.
DynamoDB supports two types of secondary indexes: Global secondary index — An index with a partition key and a sort key that can be different from those on the base table. A global secondary index is considered "global" because queries on the index can span all of the data in the base table, across all partitions.
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.
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With