Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

initial/updated rotating message tables don't respect read/write_throughput settings #928

Closed
pjenvey opened this issue Jun 20, 2017 · 0 comments
Closed

initial/updated rotating message tables don't respect read/write_throughput settings #928

pjenvey opened this issue Jun 20, 2017 · 0 comments
Assignees
@pjenvey
Labels
bug

Comments

@pjenvey
Copy link
Member

pjenvey commented Jun 20, 2017

AutopushSettings's initial call of get_rotating_message_tables utilizes its throughput values, yet other methods that potentially create tables don't.

This isn't overridden by ops and the lambda script handles it anyway, so not super important
@pjenvey pjenvey added the bug label Jun 20, 2017
@pjenvey pjenvey self-assigned this Jun 20, 2017
@pjenvey pjenvey mentioned this issue Jul 17, 2017
Closed
pjenvey added a commit that referenced this issue Jul 24, 2017
@pjenvey
refactor: postpone any db table creation/lookup into db.setup()
85b5b8b 
specify read/write_throughput settings in initial/update rotating
tables

remove some unneeded moto usage

Closes #956
Closes #928
pjenvey added a commit that referenced this issue Jul 27, 2017
@pjenvey
refactor: postpone any db table creation/lookup into db.setup()
4e78174 
specify read/write_throughput settings in initial/update rotating
tables

remove some unneeded moto usage

Closes #956
Closes #928
@pjenvey pjenvey mentioned this issue Jul 27, 2017
Merged
pjenvey added a commit that referenced this issue Jul 27, 2017
@pjenvey
refactor: postpone any db table creation/lookup into db.setup()
a75aec9 
specify read/write_throughput settings in initial/update rotating
tables

remove some unneeded moto usage

Closes #956
Closes #928
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@pjenvey pjenvey

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pjenvey @jrconlin