Import GES

Updated on 2022-02-22 GMT+08:00

View PDF

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.

**Table 1** Parameters of Import GES nodes
Parameter	Mandatory	Description
Node Name	Yes	Name of the node. Must consist of 1 to 128 characters and contain only letters, digits, underscores (_), hyphens (-), slashes (/), less-than signs (<), and greater-than signs (>).
Graph Name	Yes	Select the graph to be imported. To create a GES graph, go to the GES console.
Metadata	Yes	Select the corresponding metadata.
Edge Dataset	Yes	Select the corresponding edge dataset.
Vertex Dataset	No	Select the corresponding vertex dataset. If it is not selected, the vertices in the edge dataset are used as the source of the vertex dataset.
Edge Processing	Yes	The edge processing supports the following modes: Allow repetitive edges Ignore subsequent repetitive edges Overwrite previous repetitive edges
Offline	No	Indicates whether offline import is selected. The value is true or false, and the default value is false. true: Offline import is selected. The import speed is high, but the graph is locked and cannot be read or written during the import. false: Online import is selected. Compared with offline import, online import is slower. However, the graph can be read (cannot be written) during the import.
Ignore Labels on Repetitive Edges	No	Indicates whether to ignore labels on repetitive edges. The value is true or false, and the default value is true. true: Indicates that the repetitive edge definition does not contain the label. That is, the <source vertex, target vertex> indicates an edge, excluding the label information. false: Indicates that the repetitive edge definition contains the label. That is, the <source vertex, target vertex, label> indicates an edge.
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.

**Table 2** Advanced parameters
Parameter	Mandatory	Description
Node Status Polling Interval (s)	Yes	Specifies how often the system check completeness of the node task. 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 not be retried and is set to the failed state.
Retry upon Failure	Yes	Indicates whether to re-execute a node task if its execution fails. Possible values: Yes: The node task will be re-executed, and the following parameters must be configured: Maximum Retries Retry Interval (seconds) No: The node task will not be re-executed. This is the default setting. NOTE: If Timeout Interval is configured for the node, the node will not be executed again after the execution times out. Instead, the node is set to the failure state.
Failure Policy	Yes	Operation that will be performed if the node task fails to be executed. Possible values: End the current job execution plan Go to the next job Suspend the current job execution plan Suspend execution plans of the current and subsequent nodes

Parent topic: Nodes

Previous topic: Rest Client

Next topic: MRS Kafka

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot