DynamoDB model is out of date?

It looks like specifying hash keys and range keys separately is now deprecated. The new way is to specify them together.

This is how the problem exhibits itself on my side:

        items = self.dbclient.batch_get_item(
            RequestItems={
                self.urls_table_name: {
                    "ConsistentRead": True,
                    "ExpressionAttributeNames": {"#U": "url"},
                    "ProjectionExpression": "#U,elastic_id",
                    "Keys": [{"url": {"S": u}} for u in urls]
                }
            }
        )

The above code ends up tripping over KeyError: u’HashKeyElement’.

[bblommers]

@crbunney It looks like you’re using the old API version of DynamoDB. Are you getting the same error with @mock_dynamodb2?

[crbunney]

No, not when I use @mock_dynamodb2 (found that suggestion on the different issue after I posted this)

Although, I find it a bit counterintuitive. There’s no dynamodb2 in boto3 (only in prior boto versions) and for other usages, the argument passed to the resource/client call matches the mock decorator (e.g. resource('dynamodb') implies using @moto.mock_dynamodb, not @moto.mock_dynamodb2)

So it looks like the old API has been completely deprecated in boto3 and replaced with the “new” API (although the new one isn’t really new any more, it’s been around for, what, 5 years?)