Batch Exporting Jobs

Function

This API is used to batch export jobs, including job dependency scripts and CDM job definitions.

Authorization Information

Each account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions.

• If you are using role/policy-based authorization, see Permissions Policies and Supported Actions for details on the required permissions.
• If you are using identity policy-based authorization, no identity policy-based permission required for calling this API.

URI

• URI format

  POST /v1/{project_id}/jobs/batch-export

• Parameter description

  Table 1 URI parameter

  Parameter	Mandatory	Type	Description
  project_id	Yes	String	Project ID. For details about how to obtain a project ID, see Project ID and Account ID.

Request Parameters

Response Parameters

The response message of batch exporting jobs is the same as that of exporting jobs. For details, see Response Parameters.

Example Request

POST /v1/b384b9e9ab9b4ee8994c8633aabc9505/jobs/batch-export
{
   "jobList":["job_batch","job_stream"],
   "exportDepend":true
}

Example Response

• Success response

  The value of Content-Type in the response message is application/octet-stream that needs to be converted into a file. For details, see Parsing a Stream in a Response Message. The response is a compressed file named jobs.zip. The file structure after decompression is as follows:

  jobs
  +---job_batch
  |       dws_sql.script
  |       job_batch.job
  \---job_stream
  job_stream.job

  job_batch.job and job_stream.job are job definition files.

  dws_sql.script is the DWS SQL script file used by job_batch.job.

• Failure response

  HTTP status code 400

  {
      "error_code":"DLF.3051",
      "error_msg":"The request parameter is invalid."
  }