In DataWorks, you can use a Doris node to develop, periodically schedule, and integrate Doris tasks with other jobs. This topic describes how to develop these tasks.
Background
Apache Doris is a high-performance, real-time analytical database. It is well-suited for use cases such as report analysis, ad hoc queries, and accelerating data lake federated queries. For more information, see Introduction to Apache Doris.
Prerequisites
-
The business process has been created.
Data Studio performs engine-specific development operations based on business flows. Before creating a node, create a business flow first. For more information, see Create a business flow.
-
A Doris data source is created.
You must add your Doris database as a Doris data source in DataWorks before you can access its data. For more information about creating a data source, see Manage data sources. For more information about using a Doris data source in DataWorks, see Doris data source.
NoteDoris nodes support only Doris data sources that are created by using a JDBC connection string.
-
A network connection is established between your data source and a resource group.
You must make sure that the desired data source is connected to the resource group that you want to use. For more information about how to configure network connectivity, see Establish a network connection between a resource group and a data source.
-
(Optional; required for Resource Access Management (RAM) users) The RAM user used for task development has been added to the target workspace and assigned either the Development or Workspace Administrator role (which grants broad permissions—assign with caution). For more information about adding members and granting permissions, see Add members to a workspace.
Limitations
Doris nodes are supported in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Chengdu), China (Hong Kong), Japan (Tokyo), Singapore, Malaysia (Kuala Lumpur), Germany (Frankfurt), US (Silicon Valley), and US (Virginia).
Step 1: Create a Doris node
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
-
Right-click the target workflow and choose .
-
In the Create Node dialog box, enter a Name for the node and click OK. After the node is created, you can develop and configure its task.
Step 2: Develop the Doris task
(Optional) Select a Doris data source
If your workspace has multiple Doris data sources, you must select the appropriate one on the node's editor page. If only one Doris data source exists, it is used by default.
Doris nodes support only Doris data sources that are created by using a JDBC connection string.
Develop SQL code: Simple example
In the code editor of the Doris node, write the SQL for your task. The following is a sample:
SELECT * FROM usertablename;
Develop SQL code: Use scheduling parameters
DataWorks provides Scheduling Parameter to pass dynamic values to your code for periodic tasks. You can define variables in your task code by using the ${variable_name} format. Then, in the right-side navigation pane of the node editor, go to the Properties tab and use the Scheduling Parameter section to assign a value to the variable. For more information about supported formats and configuration details, see Supported formats of scheduling parameters and Configure and use scheduling parameters.
The following sample code demonstrates this:
SELECT '${var}'; -- You can use scheduling parameters with this code.
Step 3: Configure task scheduling
To periodically run the node task, click Scheduling on the right side of the node editing page and configure scheduling settings based on your needs. For more information, see Overview of task scheduling properties.
You must configure the node’s Rerun attribute and Parent Nodes before you can submit the node.
Step 4: Test task code
Perform the following test operations as needed to verify that the task behaves as expected.
-
(Optional) Select a resource group and assign custom parameter values.
-
Click the
icon in the toolbar. In the Parameter dialog box, select the schedule resource group for testing. -
If your task code uses scheduling parameter variables, assign values to them here for testing. For more information about parameter assignment logic, see Task debugging process.
-
-
Save and run the task code.
Click the
icon in the toolbar to save your task code. Then click the
icon to run the task. -
(Optional) Perform smoke testing.
To run smoke testing in the development environment and verify that the scheduled node task executes as expected, perform smoke testing either during or after node submission. For more information, see Perform smoke testing.
Step 5: Submit and publish the task
After configuring the node task, submit and publish it. Once published, the node runs periodically based on its scheduling configuration.
-
Click the
icon in the toolbar to save the node. -
Click the
icon in the toolbar to submit the node task.In the Submission dialog box, enter a Change Description. Optionally, choose whether to require code review after submission.
Note-
You must configure the node’s Rerun attribute and Parent Nodes before you can submit the node.
-
Code review helps ensure code quality and prevents errors caused by unreviewed code being published directly to production. If code review is enabled, the submitted node code must be approved by reviewers before it can be published. For more information, see Code review.
-
If you are using a workspace in standard mode, after successfully submitting the task, click Publish in the upper-right corner of the node editing page to deploy the task to the production environment. For more information, see Publish a task.
Next steps
Task operations: After a task is committed and published, it runs periodically based on the node's configuration. You can click O&M in the top-right corner of the node editing page to go to the Operation Center and view the scheduling and running status of the scheduled task. For more information, see Managing Scheduled Tasks.