mboudreau / Alternator

A mock DynamoDB that runs locally for testing purposes - DEPRECATED, PLEASE USE DYNAMODB LOCAL: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html
Apache License 2.0
78 stars 39 forks source link

Can't create a table with throughput greater than 116 #77

Closed irakitin closed 11 years ago

irakitin commented 11 years ago

Limits.java public static final int NUMBER_MAX = 10^+126;

This actually equals to 116 and ProvisionedThroughputValidator gets an error when trying to supply values for throughput greater than 116.

mboudreau commented 11 years ago

Whoops, what an oversight! Thanks for letting me know, I'll fix it tonight.

mboudreau commented 11 years ago

Fixed and deployed new version, 0.6.6. Cheers.

irakitin commented 11 years ago

Seems like (int)Math.pow(10, 126) is -1. Why do you need this strange limit? Why not use Integer.MAX_VALUE for instance?

mboudreau commented 11 years ago

I just debugged and it gave me the property number. It's not an integer value limit, it's an amazon specific one. On Sep 18, 2013 2:59 AM, "Ilya Rakitin" notifications@github.com wrote:

Seems like (int)Math.pow(10, 126) is -1. Why do you need this strange limit? Why not use Integer.MAX_VALUE for instance?

— Reply to this email directly or view it on GitHubhttps://github.com/mboudreau/Alternator/issues/77#issuecomment-24604558 .

mboudreau commented 11 years ago

Shoot, stupid me, the int value limits it. Need to change it to a double. Will fix again tonight and redeploy. On Sep 18, 2013 9:00 AM, "Michel Boudreau" michelboudreau@gmail.com wrote:

I just debugged and it gave me the property number. It's not an integer value limit, it's an amazon specific one. On Sep 18, 2013 2:59 AM, "Ilya Rakitin" notifications@github.com wrote:

Seems like (int)Math.pow(10, 126) is -1. Why do you need this strange limit? Why not use Integer.MAX_VALUE for instance?

— Reply to this email directly or view it on GitHubhttps://github.com/mboudreau/Alternator/issues/77#issuecomment-24604558 .

mboudreau commented 11 years ago

properly fixed in 0.6.7. Sorry about that.