You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The syntax example for GetStatementResultCommand shows GetStatementResultRequest as the type for the input GetStatementResultResponse as the type for the output. However, below the example it shows GetStatementResultCommandInput as the input type and GetStatementResultCommandOutput as the output type.
Hi @DevonStern - thanks for reaching out and sorry about the confusion around this.
The behavior you're seeing is by design in AWS SDK for JavaScript v3, which differs from v2 in its modular structure. Each AWS service package in v3 comes with its own set of specific commands.
Let's break down your example:
The actual service API is called GetStatementResult
This API has its own request/response structure defined by the AWS service team GetStatementResultRequest/GetStatementResultResponse
The AWS JavaScript SDK v3 then wraps this API into a command pattern with its own input/output interface (client+command) GetStatementResultCommandInput/GetStatementResultCommandOutput
This pattern is consistent across all AWS services in SDK v3 docs. For instance, you'll see the same structure in other services like S3's PutObjectCommand.
In that case, it might be that some other pages need to have their examples updated to match that pattern. For example, on the pages for ExecuteStatementCommand and BatchExecuteStatementCommand it shows input/output as the types in the example rather than request/response. Is that correct?
Describe the issue
The syntax example for GetStatementResultCommand shows
GetStatementResultRequest
as the type for the inputGetStatementResultResponse
as the type for the output. However, below the example it showsGetStatementResultCommandInput
as the input type andGetStatementResultCommandOutput
as the output type.Links
https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/client/redshift-data/command/GetStatementResultCommand/
The text was updated successfully, but these errors were encountered: