This topic describes how to commit nodes to Operation Center for testing after you configure the nodes.
- Optional. Commit a workflow. If you have committed nodes and have not modified the
nodes after you configure them, skip this step.
- Double-click the Workshop workflow. Then, click the icon.
- Select all nodes that can be committed and Ignore I/O Inconsistency Alerts. Then, click Commit.
Note In a workspace in standard mode, after you commit the nodes, you must click Deploy and deploy the nodes to the production environment.
- Click Operation Center in the upper-right corner.
- In the left-side navigation pane, choose . Double-click the start node in the node list.
- In the directed acyclic graph (DAG) that appears on the right, right-click the start
node and choose
- In the Patch Data dialog box, select the nodes for which retroactive data needs to be generated, set the data timestamp to the last week, and then click OK.
- In the left-side navigation pane, click Patch Data. View the running status of retroactive instances. You can click Refresh to refresh the page and view the running status of the instances in real time.
If a retroactive instance is abnormal, right-click the corresponding node in the DAG, select View Runtime Log, and then fix the issue.
- After the retroactive instances are run, verify the results.
- In the left-side navigation pane, click the Workshop workflow and then . Right-click Data Analytics and choose . Create an ODPS SQL node named query.
- To check whether data is written to the rpt_user_trace_log table, enter the following
SQL statement to query data from June 11, 2019 to June 17, 2019 in the rpt_user_trace_log
select * from rpt_user_trace_log where dt BETWEEN '20190611' and '20190617' limit 1000;
- Click the icon.
The following figure shows the query results.