...

Step -

...

Create Output Objects

Before you run a job. In the above example, you must run the job for the terminal dataset, which is POS-r01 in this case. This dataset contains references to all of the other datasets. When the job is run, the recipes for the other datasets are also applied to the terminal dataset, which ensures that the output reflects the proper integration of these other datasets into POS-r01. 

Steps:

...

...

Request Body:

{
  "wrangledDataset": {
    "id": 23
  },
  "overrides": {
    "execution": "photon",
    "profiler": true,
    "writesettings": [
      {
        "path": "hdfs://hadoop:50070/trifacta/queryResults/admin@example.com/POS-r01.csv",
        "action": "create",
        "format": "csv",
        "compression": "none",
        "header": false,
        "asSingleFile": false
      }
    ]
  },
  "ranfrom": null
}

...

...

1. Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
2. Output is written as a new file with no overwriting of previous files.

...

define output objects, which specify the following:

• Running environment where the job is executed
• Profiling on or off
• outputObjects have the following objects associated with them:
  • writeSettings: These objects define the file-based outputs that are produced for the output object
  • publications: These objects define the database target, table, and other settings for publication to a relational datastore. 

For more information on creating outputObjects, writeSettings, and publications, see API Workflow - Manage Outputs.

Step - Run Job

Through the APIs, you can specify and run a job. In the above example, you must run the job for the terminal dataset, which is POS-r01 in this case. This dataset contains references to all of the other datasets. When the job is run, the recipes for the other datasets are also applied to the terminal dataset, which ensures that the output reflects the proper integration of these other datasets into POS-r01. 

Steps:

1. Acquire the internal identifier for the recipe for which you wish to execute a job. In the previous example, this identifier was 23.
2. Construct a request using the following:

    

   Endpoint	http://www.example.com:3005/v4/jobGroups
   Authentication	Required
   Method	POST

   Request Body:

   Code Block

   { "wrangledDataset": { "sessionIdid": "79276c31-c58c-4e79-ae5e-fed1a25ebca1",23 }, "overrides": { "reasonexecution": "JobStartedphoton", "jobGraphprofiler": {true, "verticeswritesettings": [ 21,{ 22 "path": "hdfs://hadoop:50070/trifacta/queryResults/admin@example.com/POS-r01.csv", ]"action": "create", "edgesformat": ["csv", "compression": "none", { "header": false, "sourceasSingleFile": 21,false } "target": 22 } ] }, "idranfrom": 3, "jobs": { "data": [ { "id": 21 }, { "id": 22 } null }

   
   

3.  In the above example, the specified job has been launched for recipe 23 to execute on the

   D s photon

    running environment with profiling enabled. 
   1. Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
   2. Output is written as a new file with no overwriting of previous files.

4. A response code of 201 - Created is returned. The response body should look like the following:

   Code Block
   { "sessionId": "79276c31-c58c-4e79-ae5e-fed1a25ebca1", "reason": "JobStarted", "jobGraph": { "vertices": [ ] } }

5. Retain the id value, which is the job identifier, for monitoring.

Step - Monitoring Your Job

...

1. 21, 22 ], "edges": [ { "source": 21, "target": 22 } ] }, "id": 3, "jobs": { "data": [ { "id": 21 }, { "id": 22 } ] } }

   
   

2. Retain the id value, which is the job identifier, for monitoring.

Step - Monitoring Your Job

You can monitor the status of your job through the following endpoint:

When the job has successfully completed, the returned status message is the following:

"Complete"

For more information, see API JobGroups Create v4.

Step - Re-run Job

In the future, you can re-run the job exactly as you specified it by executing the following call:

When the job has successfully completed, the returned status message is the following:

"Complete"

For more information, see API JobGroups Create v4.

Step - Re-run Job

In the future, you can re-run the job exactly as you specified it by executing the following call:

{
  "wrangledDataset": {
    "id": 23
  },
  "overrides": {
    "execution": "photon",
    "profiler": true,
    "writesettings": [
      {
        "path": "hdfs://hadoop:50070/trifacta/queryResults/admin@example.com/POS-r01.csv",
        "action": "create",
        "format": "csv",
        "compression": "none",
        "header": false,
        "asSingleFile": false
      }
    ]
  },
  "ranfrom": null
}

The job is re-run as it was previously specified.If you need to modify any job parameters, you must create a new job definition.