waiting for table to be ready #168
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
adding myself as contributor Signed-off-by: Alessandro Moscatelli <alessandro.moscatelli@visiontech.cloud>
|
Can one of the admins verify this patch? |
|
@otaviojava Could you verify that please. It seems Github no longer shows merged PRs under the "contributors" in each repository or is this the first PR by @amoscatelli? |
|
@amoscatelli thank you for the contribuition |
|
Btw not sure, if his membership would allow that at this point, but would you also consider @amoscatelli for a committer election to JNoSQL or is it too soon for that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We were creating the table without waiting for it to be ready.
This caused the table not to be ready and a Resource not found Exception was thrown from aws.
This happens only when using in cloud dynamodb table, I could not reproduce the issue when using the local dynamodb docker instance.
Also adding myself as contributor where I previously contributed.