A DataWorks workspace in standard mode can be associated with two MaxCompute projects to isolate the development environment from the production environment. In addition, a process is added to deploy nodes, which ensures the correctness of node code.
Advantages of the standard mode
In DataWorks of the earlier versions, a DataWorks workspace is associated with a MaxCompute project. This corresponds to the basic mode in DataWorks of the new version.
Table permissions are difficult to manage in workspaces in standard mode. For example, in a workspace in basic mode, you cannot allow only specific members in the workspace to query specific tables. In the workspace that is associated with a MaxCompute project, the developer role has permissions to perform operations on all tables in the MaxCompute project. Therefore, table permissions cannot be managed in a fine-grained manner. In this case, you must create another DataWorks workspace to isolate data.
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 the need to develop code in Workspace A. In this case, Workspace A serves as the production environment, and Workspace B serves as the development environment.
However, binding two DataWorks workspaces has specific disadvantages. Workspace A is a normal workspace that allows members to develop nodes in DataStudio. Therefore, node code is still editable in Workspace A that serves as the production environment. This may affect the entire development process.
- A DataWorks workspace in standard mode can be associated with two MaxCompute projects. In this case, the compute engine for the development environment is isolated from that for the production environment. Workspace members have permissions to perform operations only in the development environment. By default, they are not allowed to perform operations on tables in the production environment. This enhances data security in the production environment.
- In standard mode, nodes that are processed in DataStudio are from the development environment. Only deployed nodes are available in the production environment. The standard mode allows members to edit node code only in the development environment. This improves code security in the production environment.
- By default, recurring nodes are not run in the development environment in standard mode. This reduces computing resources that are consumed in the development environment and reserves sufficient resources to run nodes in the production environment.
How the standard mode changes the procedures for using DataWorks
The standard mode isolates the development environment from the production environment. This changes the procedures for using DataWorks, such as the procedures of data model design, data processing, and code deployment.
Procedure for upgrading the workspace mode
You can log on to DataWorks by using an Alibaba Cloud account and perform the following operations to upgrade a workspace from the 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 workspace that you want to upgrade and click Workspace Settings in the Actions column.
- In the Workspace Settings panel, click More. The Configuration page appears.
You can also click Data Analytics in the Actions column to go to DataStudio. On the DataStudio page, click the Workspace Manage icon in the upper-right corner to go to the Configuration page.
- On the Configuration page, click Upgrade to standard mode next to Simple Mode.
- In the Upgrade to standard mode dialog box, enter a name in the MaxCompute Project Name field in the Development Environment section, select Confirm that you want to upgrade this workspace, and then click Confirm.
Notice You must create a workspace in basic mode as a MaxCompute project in the development environment. In the Compute Engine Information section of the page, you can specify a personal account or the workspace owner to perform operations on data in the production environment.
- In the Confirm upgrade message, click OK.
After the preceding operations are complete, you can go back to the Configuration page and check whether the workspace mode is displayed as Standard.
Changes brought by the upgrade from 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 upgrades Workspace A from the basic mode to the standard mode. A workspace that is 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. Only tables are created, but table data is not cloned. Developer A1 and O&M Engineer 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. By default, they are not allowed to select or drop tables. In this case, data in the production environment is protected.
By default, the project that is processed on the DataStudio page is Project A_dev. To query the data of the production environment on the DataStudio page, you must specify the table name in the format of Project name.Table name. On the DataStudio page, you can edit only the node code of Project A_dev. To update the node code in Project A, you must commit a node in Project A_dev and deploy the node to the production environment. The deployment and review of nodes ensure the correctness of node code in the production environment.
After a workspace is upgraded to the standard mode, the original roles of RAM users are deleted. If you use the AccessKey pair of a RAM user in node code, an error may be thrown to inform that you do not have permissions.
A workspace in basic mode is associated with a MaxCompute project, and an Alibaba Cloud account is specified to perform operations on the MaxCompute project. After the workspace is upgraded from the basic mode to the standard mode, the allowed operations of RAM users change. The following table describes the changes.
|Scenario||Workspace in basic mode||Workspace in standard mode|
|Perform operations on tables, resources, or functions||RAM users can directly perform operations on tables, resources, or functions.
Note In the workspace in basic mode, an Alibaba Cloud account is specified to perform operations in the workspace. RAM users have the same permissions as the Alibaba Cloud account. The Alibaba Cloud account has the highest level of permissions. Therefore, RAM users can directly perform operations on data in the production environment, and permissions cannot be managed.
|Use accounts to access environments||The workspace in basic mode has only the production environment. You can directly
run commands to perform operations on resources in the production environment.
|Access resources in an environment||projectname.tablename/resource/function||