v0.2 GSI Entity Indexes about dynamodb-toolbox HOT 2 CLOSED

Hi @justynspooner! Thanks for the note. Every entity needs to have a partitionKey (and sortKey if applicable) on the PRIMARY INDEX. Secondary indexes are copies of the data, so in order to actually add the data to DynamoDB, it needs to be added to the Primary Index first, and will then get copied over to secondary indexes if they exist. This is not a function of the library, but of DynamoDB.

So in your example above, your entity would also need to specify a partitionKey:true and a sortKey:true on two of your attributes. If you are reusing your sk as the partitionKey of your GSI1, then your config should look like this:

const MyEntity = new Entity({
    name: "MyEntity",
    attributes: {
        pk: { partitionKey: true },
        sk: { sortKey: true, partitionKey: "GSI1"},
        data: {sortKey: "GSI1"},
    },
    table: MyTable
});

Hope that makes sense,
Jeremy

from dynamodb-toolbox.

That makes perfect sense now that I see it laid out like that. Might be worth adding a small example like that to the docs for those newer to DynamoDB like myself. Thank you for the quick reply I'll go and fix my code 😄

from dynamodb-toolbox.