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.
This PR is the start of a discussion related to a few edge cases w/r/t the DynamoDB API. Specifically
There are a number of API methods that can operate on multiple tables, which creates some ambiguity as to what the speced behavior for naming should be (
batchGetItem
,batchWriteItem
, etc. https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB.html#batchWriteItem-property)There are a number of API methods that allow querying by an alternate query language named PartiQL (
executeStatement
, etc. https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB.html#executeStatement-property)There are API methods where
TableName
is not available, but a Table ARN is available (listExports
etc. https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/DynamoDB.html#listExports-property)