In standard mode, a DataWorks workspace corresponds to two MaxCompute projects to isolate the development environment from the production environment. In addition, a process is added to deploy nodes and guarantee the correctness of node scripts.
Advantages of the standard mode
In earlier versions of DataWorks, a DataWorks workspace corresponds to a MaxCompute project, which is the basic mode in the new DataWorks version.
Workspaces in basic mode may lead to uncontrollable table permissions. For example, in basic mode, you are unable to allow only some members in a workspace to query part of tables. In this DataWorks workspace that corresponds to a MaxCompute project, DataWorks developers have permissions to perform operations on all tables in the MaxCompute project. In this case, table permissions cannot be precisely controlled. To isolate data, you must create another DataWorks workspace.
DataWorks of the earlier versions allows you to manually deploy nodes and bind two workspaces. For example, if you set Workspace A as the deployment workspace of Workspace B, you can deploy nodes from Workspace B to Workspace A, without developing code. In this case, Workspace A works as the production environment, whereas Workspace B works as the development environment.
However, binding two DataWorks workspaces has certain disadvantages. As a normal DataWorks workspace, Workspace A allows members to develop nodes in DataStudio. As a result, node scripts are still editable in the production environment. This may affect the entire development process.
- A DataWorks workspace corresponds to two MaxCompute projects so that the compute engine for the development environment can be isolated from that for the production environment. Members in a workspace only have permissions to perform operations in the development environment. By default, they are not permitted to perform operations on tables in the production environment. This enhances data security in the production environment.
- In standard mode, members can process only nodes in the development environment on the DataStudio page by default. Only deployed nodes are available in the production environment. The standard mode allows members to edit node scripts only in the development environment, which protects code security in the production environment.
- In standard mode, recurring nodes are not run in the development environment by default. This can minimize computing resources consumed in the development environment and reserve sufficient resources for running nodes in the production environment.
Procedure for upgrading the workspace mode
You can log on to DataWorks with the Alibaba Cloud account and perform the following operations to upgrade a workspace in basic mode to the standard mode:
- Log on to the DataWorks console. In the left-side navigation pane, click Workspaces. On the Workspaces page, find the target workspace and click Workspace Settings in the Actions column.
- In the Workspace Settings dialog box, click More. The Workspace Management page appears.
You can also click Data Analytics in the Actions column. On the DataStudio page, click the Workspace Manage icon in the upper-right corner to go to the Workspace Management page.
- On the Workspace Management page, click Upgrade to Standard Mode next to Mode.
- In the Upgrade to Standard Mode dialog box, enter a name in the MaxCompute Project Name field for Development Environment, select Upgrade Workspace, and then click OK.
Notice You must create a workspace in basic mode as a MaxCompute project in the development environment. In addition, you can go to the Logon Account or Owner of work space in the Compute Engine section to control members who can access data in the production environment.page and select
- Click OK in the Confirm dialog box.
After completing the preceding operations, you can return to the Workspace Management page and check whether the workspace mode is displayed as Standard Mode.
Impact of upgrading the basic mode to the standard mode
After a workspace is upgraded from the basic mode to the standard mode, DataWorks clones the members of the original workspace to the newly created MaxCompute project that serves as the development environment, and retains the members and roles of the original MaxCompute project. In the MaxCompute project that serves as the production environment, DataWorks retains only the permissions of the workspace owner, but revokes the permissions of other members.
For example, a company has Workspace A in DataWorks and clicks Upgrade to Standard Mode to upgrade Workspace A from the basic mode to the standard mode. A workspace named A_dev is created to serve as the development environment. The members, roles, tables, and resources in Workspace A are all created in Workspace A_dev. Note that only tables are created, but table data is not cloned. Developer A1 and Administration expert B1 in Workspace A also join Workspace A_dev and retain their roles. Project A becomes the production environment. The permissions of members A1 and B1 in Workspace A are revoked. They are not permitted to select or drop tables by default. In this case, data in the production environment is protected.
By default, members perform operations in Project A_dev on the DataStudio page. To query data of the production environment in DataStudio, you must specify the table name in the format of Project name.Table name. On the DataStudio page, you can edit only the node scripts of Project A_dev. To update the node scripts in Project A, you must commit a node in Project A_dev and deploy the node to the production environment. By deploying and reviewing nodes, DataWorks guarantees the correctness of node scripts in the production environment.
After a workspace is upgraded to the standard mode, the original roles of Resource Access Management (RAM) users are deleted. If you use the AccessKey of a RAM user in a node script, an error may be thrown to inform that you do not have permissions.