DynamoDB API regression between 1.17.0 and 1.18.0

[mlogan]

With aws-sdk@1.17.0, I can make the following call to delete an attribute from a dynamoDB row:

updateItem({
  "TableName":"mutationTest.LOCAL",
  "Key":{"id":{"S":"1234567"}},
  "Expected":{"id":{"Exists":true,"Value":{"S":"1234567"}}},
  "AttributeUpdates":{"name":{"Action":"DELETE","Value":null}}
})

Note that AttributeUpdates contains a Value property which is set to null.

After upgrading to aws-sdk@1.18.0, I get the following error when making the above call:

ValidationException: Key datatypes must be scalars, not sets

In order to fix my application, I have to change the call to look like this:

updateItem({
  "TableName":"mutationTest.LOCAL",
  "Key":{"id":{"S":"1234567"}},
  "Expected":{"id":{"Exists":true,"Value":{"S":"1234567"}}},
  "AttributeUpdates":{"name":{"Action":"DELETE"}}
})

Note that AttributeUpdates no longer has any Value property in it.

Was this change intentional? I didn't see anything in the release notes to indicate that it was. I'm perfectly happy to be told that I've been doing it wrong all along, and the old SDK versions were simply letting me get away with it. However, a more informative error message would have saved me some headache.

Thanks!

[lsegal]

This does look like a regression. Thanks for pointing this out. In the meantime you can pass paramValidation: false to your global AWS.config or service configuration to workaround this error.

[mlogan]

It was a one-line fix to my dynamodb code to omit the Value parameter instead of setting it to null, so this is no big deal for me. The new code also works with older API versions.

[lsegal]

Thanks for reporting, @mlogan. The above fix will be part of the next release. Sorry for the headache!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.