modified: pynamodb/connection/base.py #21
Merged
Conversation
This file contains 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
jlafon
added a commit
that referenced
this pull request
May 15, 2014
modified: pynamodb/connection/base.py
|
Thanks, I'll add a test for this as well. |
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.
The following ensures the key_schema in indexes is sorted appropriately because AWS's API requires the HASH key to come first. Depending on how the stars align, you may or may not end up with your local or global index key_schema out of order resulting in the following error when creating your table:
pynamodb.exceptions.TableError: Failed to create table: {"__type":"com.amazon.coral.validate#ValidationException","message":"Invalid KeySchema: The first KeySchemaElement is not a HASH key type"