Support for the automatic parsing feature - DataWorks - Alibaba Cloud Documentation Center

This topic describes the configuration principles of the automatic parsing feature for various types of nodes. This topic also describes the scenarios in which the automatic parsing feature is not supported. You can use the automatic parsing feature based on your business requirements.

Configuration principles

The following table describes the configuration principles of the automatic parsing feature for various types of nodes.


Node type	SQL statement	Configuration based on automatic parsing	Configuration principle
ODPS node	CREATE INSERT	If the code that is developed for the node contains such SQL statements, the system automatically adds an output for the node.	The name of the output that is automatically added by the system is in the `odps_project_name.table_name` format. In the preceding format: odps_project_name: the DataWorks workspace to which the node belongs. table_name: the name of the generated table.
ODPS node	SELECT	If the code that is developed for the node contains such an SQL statement, the system automatically adds an ancestor node for the node.	The name of the ancestor node that is automatically added is named in the `project_name.table_name` format. In the preceding format: project_name: the name of the workspace to which the node that generates the table belongs. table_name: the name of the generated table.
SQL node other than the ODPS node	CREATE INSERT ALTER UPDATE	If the code that is developed for the node contains such SQL statements, the system automatically adds an output for the node.	The names of the outputs that are automatically added by the system for different nodes are in the following formats: E-MapReduce (EMR): workspace_name.db_name.table_name AnalyticDB for PostgreSQL: workspace_name.db_name.schema_name.table_name AnalyticDB for MySQL: workspace_name.db_name.schema_name.table_name Hologres: workspace_name.db_name.schema_name.table_name In the preceding formats: workspace_name: the name of the DataWorks workspace to which the node belongs. db_name: the name of the database to which the data is written. schema_name: the name of the schema of the node. table_name: the name of the generated table.
SQL node other than the ODPS node	SELECT	If the code that is developed for the node contains such an SQL statement, the system automatically adds an ancestor node for the node.	The name of the ancestor node that is automatically added by the system is in the `project_name.table_name` format. In the preceding format: project_name: the name of the workspace to which the node that generates the table belongs. table_name: the name of the generated table.
Batch synchronization node	Batch synchronization nodes do not support the automatic parsing feature. You must manually configure scheduling dependencies for this type of nodes.

Nodes that do not support the automatic parsing feature

This section describes the scenarios in which the automatic parsing feature is not supported.

Several types of nodes do not support the automatic parsing feature. You can check whether a node supports the automatic parsing feature in the DataWorks console.
For example, batch synchronization nodes and AnalyticDB for PostgreSQL nodes do not support configuration of scheduling dependencies by using the automatic parsing feature. The tables that are generated by these types of nodes must be manually added to the outputs of the nodes.
Temporary tables that are created by executing SQL statements do not support the automatic parsing feature. For example, tables whose names are prefixed with t_ in a workspace are specified as temporary tables. These tables cannot be automatically added to Output or Parent Nodes for a node.
After a table is generated on a synchronization node, you must manually add the table as the output of the node. The table name is in the projectname.tablename format. This way, the scheduling dependencies of the synchronization node can be quickly configured by using the automatic parsing feature when data of the generated table is cleansed by the descendant nodes of the synchronization node.