Import GES
Function
The Import GES node is used to import files from an OBS bucket to a GES graph.
Parameters
Table 1 and Table 2 describe the parameters of the Import GES node.
Parameter |
Mandatory |
Description |
---|---|---|
Node Name |
Yes |
Name of a node. The name must contain 1 to 128 characters, including only letters, numbers, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>). |
Graph Name |
Yes |
You can directly select the graph to import or manually enter the graph name. To create a GES graph, go to the GES console. |
Metadata Source |
Yes |
Two types of metadata sources are available:
|
Metadata |
No |
Set this parameter based on the value you select for Metadata Source.
|
Edge Data Set |
No |
You can select the edge data set CSV file in the corresponding OBS bucket or select the OBS path of the edge data set.
The vertex and edge data sets must comply with the data format requirements of GES graphs. The graph data format requirements are briefed as follows. For details, see Graph Data Formats.
|
Vertex Data Set |
No |
You can directly select the corresponding Vertex data set or select the OBS path of the Vertex data set.
The vertex and edge data sets must comply with the data format requirements of GES graphs. The graph data format requirements are briefed as follows. For details, see Graph Data Formats.
|
Edge Processing |
Yes |
The edge processing supports the following modes:
|
Offline |
No |
Whether offline import is used. The value is Yes or No, and the default value is No.
|
Ignore Labels on Repetitive Edges |
No |
Indicates whether to ignore labels on repetitive edges. The value is Yes or No, and the default value is Yes.
|
Log Storage Path |
No |
Stores vertex and edge datasets that do not comply with the metadata definition, as well as detailed logs generated during graph import. |
Parameter |
Mandatory |
Description |
---|---|---|
Node Status Polling Interval (s) |
Yes |
How often the system check completeness of the node. The value ranges from 1 to 60 seconds. |
Max. Node Execution Duration |
Yes |
Execution timeout interval for the node. If retry is configured and the execution is not complete within the timeout interval, the node will be executed again. |
Retry upon Failure |
Yes |
Whether to re-execute a node if it fails to be executed. Possible values:
|
Policy for Handling Subsequent Nodes If the Current Node Fails |
Yes |
Operation that will be performed if the node fails to be executed. Possible values:
|
Enable Dry Run |
No |
If you select this option, the node will not be executed, and a success message will be returned. |
Task Groups |
No |
Select a task group. If you select a task group, you can control the maximum number of concurrent nodes in the task group in a fine-grained manner in scenarios where a job contains multiple nodes, a data patching task is ongoing, or a job is rerunning. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot