Issue #17 - Create table when not exist #219
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
derjust
force-pushed
the
Issue-17
branch
2 times, most recently
from
e9a2b60 to
51cc075
Compare
Codecov Report
@@ Coverage Diff @@
## master #219 +/- ##
===========================================
+ Coverage 65.4% 67.31% +1.9%
- Complexity 600 656 +56
===========================================
Files 77 83 +6
Lines 2038 2227 +189
Branches 374 392 +18
===========================================
+ Hits 1333 1499 +166
+ Misses 550 549 -1
- Partials 155 179 +24
Continue to review full report at Codecov.
|
derjust
force-pushed
the
Issue-17
branch
8 times, most recently
from
6e7f61c to
8513654
Compare
derjust
force-pushed
the
Issue-17
branch
2 times, most recently
from
dcf0160 to
9566c39
Compare
derjust
force-pushed
the
Issue-17
branch
4 times, most recently
from
714b1d9 to
9d6fa71
Compare
A new property is introduced to automatically handle table creation (Key columns + GSIs): `spring.data.dynamodb.entity2ddl.auto` That can be any of the following settings * `none` - The default. No action performed * `create-only` - Tables are created on Spring startup if table doesn't exist * `drop` - Tables are dropped on Spring context shutdown * `create` - Tables are dropped & created on Spring startup * `create-drop` - Tables are dropped & created on Spring startup and dropped on shutdown * `validate` - The existing tables are checked to exist - otherwise an Exception is generated on Spring context startup There are additional settings for the creation of tables: `spring.data.dynamodb.entity2ddl.gsiProjectionType`: The projection type for the GSIs * `ALL` * `KEYS_ONLY` * `INCLUDE` Please consult `com.amazonaws.services.dynamodbv2.model.ProjectionType` `spring.data.dynamodb.entity2ddl.readCapacity` (default `10`): The read capacity for the GSIs & the table itself `spring.data.dynamodb.entity2ddl.writeCapacity` (default `1`): The write capacity for the GSIs & the table itself To achieve this, some substantial refactoring was required as a lot of objects were created outside of the Spring context. All changes should be backward compatible and not change any semantic but if anything is broken - please report!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.