RedshiftDataAPIService / Client / batch_execute_statement

batch_execute_statement#

RedshiftDataAPIService.Client.batch_execute_statement(**kwargs)#

Runs one or more SQL statements, which can be data manipulation language (DML) or data definition language (DDL). Depending on the authorization method, use one of the following combinations of request parameters:

  • Secrets Manager - when connecting to a cluster, provide the secret-arn of a secret stored in Secrets Manager which has username and password. The specified secret contains credentials to connect to the database you specify. When you are connecting to a cluster, you also supply the database name, If you provide a cluster identifier ( dbClusterIdentifier), it must match the cluster identifier stored in the secret. When you are connecting to a serverless workgroup, you also supply the database name.

  • Temporary credentials - when connecting to your data warehouse, choose one of the following options:

    • When connecting to a serverless workgroup, specify the workgroup name and database name. The database user name is derived from the IAM identity. For example, arn:iam::123456789012:user:foo has the database user name IAM:foo. Also, permission to call the redshift-serverless:GetCredentials operation is required.

    • When connecting to a cluster as an IAM identity, specify the cluster identifier and the database name. The database user name is derived from the IAM identity. For example, arn:iam::123456789012:user:foo has the database user name IAM:foo. Also, permission to call the redshift:GetClusterCredentialsWithIAM operation is required.

    • When connecting to a cluster as a database user, specify the cluster identifier, the database name, and the database user name. Also, permission to call the redshift:GetClusterCredentials operation is required.

For more information about the Amazon Redshift Data API and CLI usage examples, see Using the Amazon Redshift Data API in the Amazon Redshift Management Guide.

See also: AWS API Documentation

Request Syntax

response = client.batch_execute_statement(
    ClientToken='string',
    ClusterIdentifier='string',
    Database='string',
    DbUser='string',
    ResultFormat='JSON'|'CSV',
    SecretArn='string',
    SessionId='string',
    SessionKeepAliveSeconds=123,
    Sqls=[
        'string',
    ],
    StatementName='string',
    WithEvent=True|False,
    WorkgroupName='string'
)
Parameters:

  • ClientToken (string) –

    A unique, case-sensitive identifier that you provide to ensure the idempotency of the request.

    This field is autopopulated if not provided.

  • ClusterIdentifier (string) – The cluster identifier. This parameter is required when connecting to a cluster and authenticating using either Secrets Manager or temporary credentials.

  • Database (string) – The name of the database. This parameter is required when authenticating using either Secrets Manager or temporary credentials.

  • DbUser (string) – The database user name. This parameter is required when connecting to a cluster as a database user and authenticating using temporary credentials.

  • ResultFormat (string) – The data format of the result of the SQL statement. If no format is specified, the default is JSON.

  • SecretArn (string) – The name or ARN of the secret that enables access to the database. This parameter is required when authenticating using Secrets Manager.

  • SessionId (string) – The session identifier of the query.

  • SessionKeepAliveSeconds (integer) – The number of seconds to keep the session alive after the query finishes. The maximum time a session can keep alive is 24 hours. After 24 hours, the session is forced closed and the query is terminated.

  • Sqls (list) –

    [REQUIRED]

    One or more SQL statements to run. The SQL statements are run as a single transaction. They run serially in the order of the array. Subsequent SQL statements don't start until the previous statement in the array completes. If any SQL statement fails, then because they are run as one transaction, all work is rolled back.</p>

    • (string) –

  • StatementName (string) – The name of the SQL statements. You can name the SQL statements when you create them to identify the query.

  • WithEvent (boolean) – A value that indicates whether to send an event to the Amazon EventBridge event bus after the SQL statements run.

  • WorkgroupName (string) – The serverless workgroup name or Amazon Resource Name (ARN). This parameter is required when connecting to a serverless workgroup and authenticating using either Secrets Manager or temporary credentials.

Return type:

dict

Returns:

Response Syntax

{
    'ClusterIdentifier': 'string',
    'CreatedAt': datetime(2015, 1, 1),
    'Database': 'string',
    'DbGroups': [
        'string',
    ],
    'DbUser': 'string',
    'Id': 'string',
    'SecretArn': 'string',
    'SessionId': 'string',
    'WorkgroupName': 'string'
}

Response Structure

  • (dict) –

    • ClusterIdentifier (string) –

      The cluster identifier. This element is not returned when connecting to a serverless workgroup.

    • CreatedAt (datetime) –

      The date and time (UTC) the statement was created.

    • Database (string) –

      The name of the database.

    • DbGroups (list) –

      A list of colon (:) separated names of database groups.

      • (string) –

    • DbUser (string) –

      The database user name.

    • Id (string) –

      The identifier of the SQL statement whose results are to be fetched. This value is a universally unique identifier (UUID) generated by Amazon Redshift Data API. This identifier is returned by BatchExecuteStatment.

    • SecretArn (string) –

      The name or ARN of the secret that enables access to the database.

    • SessionId (string) –

      The session identifier of the query.

    • WorkgroupName (string) –

      The serverless workgroup name or Amazon Resource Name (ARN). This element is not returned when connecting to a provisioned cluster.

Exceptions