dynamodb : not creating correct GSI

[ETisREAL]

Describe the bug

Hello, hope you are doing fine :)

I am trying to create a dynamodb table with a GSI. This is the code:

export class LeaderboardsTableStack extends cdk.Stack {

    public leaderboardsTable

    constructor(scope: Construct, id: string, props: LeaderboardsTableStackProps) {
        super(scope, id, props)

        this.leaderboardsTable = new dynamodb.Table(this, `${props.STAGE}leaderboardsTable`, {
            tableName: `${props.STAGE}Leaderboards`,
            partitionKey: { name: 'PK', type: dynamodb.AttributeType.STRING },
            sortKey: { name: 'SK', type: dynamodb.AttributeType.STRING },
            removalPolicy: cdk.RemovalPolicy.DESTROY,
            billingMode: dynamodb.BillingMode.PROVISIONED,
            stream: dynamodb.StreamViewType.NEW_AND_OLD_IMAGES
        })

        this.leaderboardsTable.addGlobalSecondaryIndex({
            indexName: 'GSI1',
            partitionKey: { name: 'SK', type: dynamodb.AttributeType.STRING },
            sortKey: { name: 'GSI1SK', type: dynamodb.AttributeType.STRING },
            projectionType: dynamodb.ProjectionType.INCLUDE,
            nonKeyAttributes: ['participant_display_name']
        })

    }
}

Expected Behavior

Shouldn't the code above create a GSI with items that have a partition key 'SK' and a sort key 'GSI1SK'?

Current Behavior

When I deploy the above code, the GSI simply copies over the PK as primary key and SK as sort key (only for the items that conatain the GSI1SK, at least this part goes according to plan lol)

Reproduction Steps

Try to launch the above code and check the GSI creation schema

Possible Solution

No response

Additional Information/Context

No response

CDK CLI Version

2.88

Framework Version

No response

Node.js Version

v18.16

OS

Linux - Ubuntu

Language

Typescript

Language Version

No response

Other information

No response

[pahud]

Can you share the cdk synth for the Table resource especially the GlobalSecondaryIndex property?

[ETisREAL]

Hello @pahud . The issue was simply that I wasn't querying the index correctly.

For reference, I was still using PK and SK as key attributes even though I was querying on the GSI1 index, where I am supposed to use SK and GSI1SK.

Thank you @pahud for reaching out :)

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.