Create method does not create the sort key if one attribute is undefined about dynamodb-onetable HOT 4 CLOSED

Can you run with logging enabled so we can see the actual query being run.

I think if a template is incomplete - i.e. component fields are not provided, then the field is not supplied.

You could set the externalId to "" and that will probably work.

from dynamodb-onetable.

If you do a "find" / query and supply only the GSI PK, you will get all the items with that PK.

You can update items and provide the empty string externalId, that will then create the GSI item.

This is a facet of both OneTable and DyanmoDB. DynamoDb will create the item in the GSI only when complete keys are provided. OneTable will not provide a partial GSI SK. You must provide all the key components to create/update a GSI item. i.e. there must be a unique key to identify the item. When doing a find/query, you can provide only the GSI PK and it will return all matching items.

from dynamodb-onetable.

Thank you for your response. Yes, it works if I manually set the 'externalId' to "".

I think you are right, and this is inherent to dynamodb :

A global secondary index only tracks data items where its key attributes actually exist (doc aws).

--> However, I would like to be able to query all my items with the gs1pk, i.e. my 'siteId' property. Do you have a recommendation in this case ?

Possibility n°1 : Create another gsi with 'siteId' only and no gsk.

Possibility n°2 : Manually set externalId to "" at each creation. How do we do for existing items ? Update on all items to set 'externalId' to "" ?

Log of the request whithout externalId, gs1sk not provided

{
  "cmd": {
      "ConditionExpression": "(attribute_not_exists(#_0)) and (attribute_not_exists(#_1))",
      "ExpressionAttributeNames": {
          "#_0": "pk",
          "#_1": "sk"
      },
      "TableName": "clementdev-ckl-project-service-dynamodb-table",
      "Item": {
          "pk": {
              "S": "resource#7fdfac2e-63f6-4456-8d39-2c58e0c5bc7d"
          },
          "sk": {
              "S": "resource#"
          },
          "gs1pk": {
              "S": "resource#14ae59fe-2783-4501-912b-85bba7507921"
          },
          "id": {
              "S": "7fdfac2e-63f6-4456-8d39-2c58e0c5bc7d"
          },
          "siteId": {
              "S": "14ae59fe-2783-4501-912b-85bba7507921"
          },
          "_type": {
              "S": "Resource"
          }
      },
      "ReturnValues": "NONE"
  },
  "items": [
      {
          "id": "7fdfac2e-63f6-4456-8d39-2c58e0c5bc7d",
          "siteId": "14ae59fe-2783-4501-912b-85bba7507921",
      }
  ],
  "op": "put",
  "properties": {
      "pk": "resource#7fdfac2e-63f6-4456-8d39-2c58e0c5bc7d",
      "sk": "resource#",
      "gs1pk": "resource#14ae59fe-2783-4501-912b-85bba7507921",
      "id": "7fdfac2e-63f6-4456-8d39-2c58e0c5bc7d",
      "siteId": "14ae59fe-2783-4501-912b-85bba7507921",
      "_type": "Resource"
  },
  "params": {
      "parse": true,
      "high": true,
      "exists": false,
      "log": true,
      "checked": true
  }
}

from dynamodb-onetable.

That confirms what I thought. It would be great to have a warning from the library when the developer is in this scenario, because it can be a significant problem when they find out that the GSI is not updated because due to a null value.

Thank you again for your help.

from dynamodb-onetable.