Modifying a Script¶
Function¶
This API is used to modify the configuration items or script contents of a script.
When modifying a script, specify the name of the script to be modified.
The script name and type cannot be modified.
URI¶
URI format
PUT /v1/{project_id}/scripts/{script_name}
Parameter description
¶ Parameter
Mandatory
Type
Description
projectId
Yes
String
Project ID. For details about how to obtain a project ID, see Project ID and Account ID.
script_name
Yes
String
Script name.
Request Parameters¶
Parameter | Mandatory | Type | Description |
---|---|---|---|
workspace | No | String | Workspace ID.
|
Parameter | Mandatory | Type | Description |
---|---|---|---|
name | Yes | String | Script name. The name contains a maximum of 128 characters, including only letters, numbers, hyphens (-), and periods (.). The script name must be unique. |
type | Yes | String | Script type.
|
content | Yes | String | Script content. A maximum of 4 MB is supported. |
directory | No | String | Directory for storing the script. Access the DataArts Studio console and choose Data Development. In the left navigation pane, choose Development > Develop Script. In the directory tree of the script, you can view the created directories. The default directory is the root directory. |
connectionName | No | String | Name of the connection associated with the script. This parameter is mandatory when type is set to DLISQL, SparkSQL, HiveSQL, DWSSQL, Shell, PRESTO, ClickHouseSQL, HetuEngineSQL, RDSSQL, ImpalaSQL, Spark Python, or PYTHON. To obtain the existing connections, refer to the instructions in Querying a Connection List (to Be Taken Offline). By default, this parameter is left blank. |
database | No | String | Database associated with an SQL statement. This parameter is available only when type is set to DLISQL, SparkSQL, HiveSQL, DWSSQL, PRESTO, RDSSQL, ClickHouseSQL, ImpalaSQL, or HetuEngineSQL.
|
queueName | Yes | String | Queue name of the DLI resource. This parameter is available only when type is set to DLISQL. You can obtain the queue information by calling the API for "Querying All Queues" in the Data Lake Insight API Reference. By default, this parameter is left blank. |
configuration | No | map <String,Object> | Configuration defined by a user for the job. This parameter is available only when type is set to DLISQL. For details about the supported configuration items, see conf parameter description in the "Submitting a SQL Job" section of the Data Lake Insight API Reference. By default, this parameter is left blank. |
description | No | String | Description of the script. The description contains a maximum of 255 characters. |
approvers | No | List<JobApprover> | Script approver. This parameter is required if the review function is enabled. For details, see Table 4. |
Parameter | Mandatory | Type | Description |
---|---|---|---|
approverName | Yes | String | Approver name |
Response Parameters¶
None.
Example Request¶
Modify a script named echoTimeShell whose type is Shell, content is echo a, and associated connection is con.
PUT /v1/b384b9e9ab9b4ee8994c8633aabc9505/scripts/echoTimeShell
{
"name": "echoTimeShell",
"type": "Shell",
"content": "echo a",
"connectionName": "con"
}
Change the script content when the review function is enabled.
PUT /v1/b384b9e9ab9b4ee8994c8633aabc9505/scripts/echoTimeShell
{
"name": "echoTimeShell",
"type": "Shell",
"content": "echo a",
"connectionName": "con",
"approvers": [
{
"approverName": "userName1"
},
{
"approverName": "userName2"
}
]
}
Example Response¶
Success response
HTTP status code 204
Failure response
HTTP status code 400
{ "error_code":"DLF.6201", "error_msg":"The script does not exist." }