Immediately Starting a Data-level Table Comparison Task
Function
This API is used to immediately start a data-level table comparison task.
URI
POST /v3/{project_id}/jobs/{job_id}/table/compare/{compare_job_id}
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        project_id  | 
      
        Yes  | 
      
        String  | 
      
        Project ID of a tenant in a region. For details, see Obtaining a Project ID.  | 
     
| 
        job_id  | 
      
        Yes  | 
      
        String  | 
      
        Task ID.  | 
     
| 
        compare_job_id  | 
      
        Yes  | 
      
        String  | 
      
        ID of a comparison task.  | 
     
Request Parameters
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        Content-Type  | 
      
        Yes  | 
      
        String  | 
      
        The content type. The default value is application/json.  | 
     
| 
        X-Auth-Token  | 
      
        Yes  | 
      
        String  | 
      
        User token obtained from IAM.  | 
     
| 
        X-Language  | 
      
        No  | 
      
        String  | 
      
        Request language type. Default value: en-us Enumerated values: 
  | 
     
Response Parameters
None
Example Request
Immediately starting a data-level table comparison task
https://{endpoint}/v3/054ba152d480d55b2f5dc0069e7ddef0/jobs/f8688cfa-4e05-406f-a2e6-37a773cjb20y/table/compare/48c6acb4-1473-48fd-8676-df3705758c27
 Example Response
Status code: 200
OK
{ }
  Status code: 400
Bad Request
{
  "error_code" : "DRS.M00202",
  "error_msg" : "The value of jobId is invalid."
}
 Status Code
| 
        Status Code  | 
      
        Description  | 
     
|---|---|
| 
        200  | 
      
        OK  | 
     
| 
        400  | 
      
        Bad Request  | 
     
Error Code
For details, see Error Code.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.