question-mark

Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Incorrect ValidationException: No provisioned throughput specified for the table

See original GitHub issue

Issue Description

Actual Behaviour

AWS announced support for an automatic provisioning pricing plan. More info: https://medium.com/@softprops/putting-dynamodb-scalability-knobs-on-auto-pilot-3af8520439c9.

In short, you can set BillingMode: PAY_PER_REQUEST and remove the ProvisionedThoughput section. But at the moment serverless-dynamodb-local does not support this:

  Validation Exception -----------------------------------

  No provisioned throughput specified for the table

Expected Behaviour

No validation error

Steps to reproduce it

Create a template using BillingMode: PAY_PER_REQUEST: https://gist.githubusercontent.com/softprops/58c60a1ca2a8e97d6ef63bda3d3c8a9f/raw/27d2721f1d1837e3cca00f854810f484f9239ad4/serverless.yml

Would you like to work on the issue?

Yes

Issue Analytics

  • State:open
  • Created 4 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

7reactions
jslowackcommented, Dec 10, 2018

@c-neves monkey patch does not take Global Secondary Indexes into account. I’ve created a PR which modifies the migrations object in the createTable function for both tables and indexes. Feel free to give some remarks.

PR: https://github.com/99xt/serverless-dynamodb-local/pull/190

4reactions
jslowackcommented, Dec 4, 2018

I’ve just upgraded aws-sdk to 2.368 but the issue persists. I think the problem is caused by the local DynamoDb instance (https://github.com/99xt/dynamodb-localhost/).

In the AWS Docs:

Provisioned throughput settings are ignored in downloadable DynamoDB, even though the CreateTable operation requires them. For CreateTable, you can specify any numbers you want for provisioned read and write throughput, even though these numbers are not used. You can call UpdateTable as many times as you want per day. However, any changes to provisioned throughput values are ignored.

I just tried to run sls dynamodb migrate on a local DynamoDb using a Docker image (https://hub.docker.com/r/amazon/dynamodb-local/), but the problem isn’t solved.

If I’m correct, Amazon should update the implementation of the local DynamoDb instance.

Read more comments on GitHub >

github_iconTop Results From Across the Web

No provisioned throughput specified for the table · Issue #189 ...
I've just upgraded aws-sdk to 2.368 but the issue persists. I think the problem is caused by the local DynamoDb instance (https://github.com/ ...
Read more >
Unable to create table in DynamoDB with billing mode set to ...
An error occurred (ValidationException) when calling the CreateTable operation: No provisioned throughput specified for the table.
Read more >
CreateTable - Amazon DynamoDB - AWS Documentation
Represents the provisioned throughput settings for a specified table or index. The settings can be modified using the UpdateTable operation. If you set...
Read more >
Common DynamoDB Errors (and Solutions) - Dynobase
DynamoDB not working as expected? ... AttributeValue may not contain an empty string · Error ValidationException: One or more parameter values were invalid: ......
Read more >
Managing Global Secondary Indexes - Amazon DynamoDB
However, you can modify the provisioned throughput of these other indexes. Backfilling. For each item in the table, DynamoDB determines which set of ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found