...
Endpoint | http://www.example.com:3005/v4/jobGroups |
---|
Authentication | Required |
---|
Method | POST |
---|
Request Body |
Code Block |
---|
{
"wrangledDataset": {
"id": 127
},
"overrides": {
"execution": "photon",
"profiler": true,
"writesettings": [
{
"path": "MyFiles/queryResults/joe@example.com/2018-04-03-orders.csv",
"action": "create",
"format": "csv",
"compression": "none",
"header": false,
"asSingleFile": false
}
]
},
"runParameters": {}
} |
|
---|
- In the above example, the job has been launched for recipe
127
to execute on the running environment with profiling enabled. - Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
- Output is written as a new file with no overwriting of previous files.
A response code of 201 - Created
is returned. The response body should look like the following:
Code Block |
---|
{
"reasonsessionId": "JobStarted79276c31-c58c-4e79-ae5e-fed1a25ebca1",
"sessionIdreason": "5b883530-3920-11e8-a37a-db6dae3c6e43",JobStarted",
"jobGraph": {
"idvertices": 29
} |
Retain the jobgroupId=29
value for monitoring.
Example 2 - Dataset with Variable
In the following example, the region
variable has been overwritten with the value central
to execute the job on orders-central.csv
:
Endpoint | http://www.example.com:3005/v4/jobGroups |
---|
Authentication | Required |
---|
Method | POST |
---|
Request Body | Code Block |
{
"wrangledDataset": {id123},"overrides":{"execution": "photon","profiler":true,writesettings[{path"MyFiles/queryResults/joe@example.com/region-eastern.csv","action":"create","format":"csv",compression"none",
headerfalse,asSingleFilefalse}] }"runParameters":{"overrides":{data[{"key": "region""value": "central"}- In the above example, the job has been launched for recipe
123
to execute on the running environment with profiling enabled. - Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
- Output is written as a new file with no overwriting of previous files.
A response code of 201 - Created
is returned. The response body should look like the following:Retain the jobgroupId=29
value for monitoring.
Example 2 - Dataset with Variable
In the following example, the region
variable has been overwritten with the value central
to execute the job on orders-central.csv
:
Endpoint | http://www.example.com:3005/v4/jobGroups |
---|
Authentication | Required |
---|
Method | POST |
---|
Request Body |
Code Block |
---|
{
"wrangledDataset": {
" |
|
---|
reasonJobStarted,sessionIdaa0f9f00-391f-11e8-a37a-db6dae3c6e43id 27
}Retain the jobgroupId=27
value for monitoring.
Example 3 - Dataset with pattern parameter
In the following example, the value 02
has been inserted into the pattern to execute the job on POS-r02.csv
:
Info |
---|
NOTE: You cannot apply overrides to these types of datasets with parameters. |
Endpoint | http://www.example.com:3005/v4/jobGroups |
---|
Authentication | Required |
---|
Method | POST |
---|
Request Body | Code Block |
---|
{
"wrangledDataset": { true,
"writesettings": [
{
"path": "MyFiles/queryResults/joe@example.com/region-eastern.csv",
"action": "create",
"format": "csv",
"compression": "none",
"idheader": 121false,
}, "overridesasSingleFile": { false
}
]
}
"executionrunParameters": "photon",{
"profileroverrides": {
false, "writesettingsdata": [{
{ "key": "region",
"pathvalue": "hdfs://hadoop:50070/trifacta/queryResults/admin@example.com/POS-r02.txt","central"
}
"action": "create", ]}
"format": "csv",
"compression": "none",
}
} |
|
---|
- In the above example, the job has been launched for recipe
123
to execute on the running environment with profiling enabled. - Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
- Output is written as a new file with no overwriting of previous files.
A response code of 201 - Created
is returned. The response body should look like the following:
headerfalse,
"79276c31-c58c-4e79-ae5e-fed1a25ebca1",
|
asSingleFilefalse
"JobStarted",
"jobGraph": {
"vertices": [
|
}]}"runParameters": {}
}- In the above example, the job has been launched for recipe
121
to execute on the running environment with profiling enabled. - Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
- Output is written as a new file with no overwriting of previous files.
A response code of 201 - Created
is returned. The response body should look like the following:
Code Block |
---|
{
"reason": "JobStarted",
"sessionId": "16424a60-3920-11e8-a37a-db6dae3c6e43", 22
],
"edges": [
{
"source": 21,
"target": 22
}
]
},
"id": 27,
"jobs": {
"data": [
{
"id": 21
},
{
"id": 22
}
]
}
} |
Retain the jobgroupId=27
value for monitoring.
Example 3 - Dataset with pattern parameter
In the following example, the value 02
has been inserted into the pattern to execute the job on POS-r02.csv
:
Info |
---|
NOTE: You cannot apply overrides to these types of datasets with parameters. |
Endpoint | http://www.example.com:3005/v4/jobGroups |
---|
Authentication | Required |
---|
Method | POST |
---|
Request Body |
Code Block |
---|
{
"wrangledDataset": {
"id": 121
},
"overrides": {
"execution": "photon",
"profiler": false,
"writesettings": [
{
"path": "hdfs://hadoop:50070/trifacta/queryResults/admin@example.com/POS-r02.txt",
"action": "create",
"format": "csv",
"compression": "none",
"header": false,
"asSingleFile": false
}
]
},
"runParameters": {}
} |
|
---|
- In the above example, the job has been launched for recipe
121
to execute on the running environment with profiling enabled. - Output format is CSV to the designated path. For more information on these properties, see API JobGroups Create v4.
- Output is written as a new file with no overwriting of previous files.
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": [
21,
22
],
"edges": [
{
"source": 21,
"target": 22
}
]
},
"id": 28,
"jobs": {
"data": [
{
"id": 21
},
{
"id": 28 22
}
]
}
} |
Retain the jobgroupId=28
value for monitoring.
...