Enter the WeData console project list page and click on Create Project.
Parameter Configuration
Configure various parameters on the creation interface, as described in the table below:
Classification
Parameter
Description
Creation Method
Creation Type
You can choose between "Create and configure project" and "Create project only" as the project creation methods.
Basic Information
Project Identifier
Project English ID, unique within the region. Begins with a letter, may include letters, numbers, and underscores, and does not exceed 20 characters.
Project Name
Project Chinese Display Name, unique within the region. Begins with a letter or Chinese character, may include letters, Chinese characters, numbers, and underscores.
Description
Provide a simple description for the created space.
Select Engine Type
Elastic MapReduce
After activation, you can use EMR in WeData for developing big data processing tasks.
Cloud Data Warehouse TCHouse-P
After activation, you can use Cloud Data Warehouse TCHouse-P in WeData.
DLC
After activation, you can use Tencent Cloud DLC in WeData.
Configure the compute-storage engine
Region
Select the region where the Compute Engine Instance is located in WeData. Instances of different types of computing engines must be in the same region.
EMR Cluster
Select an EMR Cluster available to the current tenant in the selected region. WeData only supports EMR that includes the Hive component. If there are no available clusters, you can go to purchase an instance.
DLC
Computing Resources
Select one of the available DLC computing resources for the current tenant in the selected region.
secretId
Please go to the Tencent Cloud Certificate Authority Management CAM consoleAPI Key Management page, copy SecretId and SecretKey to fill in the current input box.
If there are restrictions on the permission control scope, you canapply for a Sub-accountand fill in the corresponding SecretId and SecretKey.
Once activated, a collection task will automatically be created. After completing the Resource Group Configuration, the collection task will collect and analyze metadata from the engine. You can go to the Data Operation Module to view and modify the task.
TCHouse-P Cluster
TCHouse-P Version
You can choose the TCHouse-P1.0 or TCHouse-P2.0 version.
Cluster Name
The name of the TCHouse-P Cluster already purchased by the account in the selected region.
Password
The password for connecting to the TCHouse-P Cluster.
Testing connectivity
Test whether the password can connect to the cluster. If the connection test passes, you can create a project (if the connectivity test fails, it may be because WeData is blocked by the network firewall where the cluster is located).
Execute Resource Allocation
Scheduling Resources
Scheduling Resources
Scheduling resources are principally used for the timed scheduling of data development tasks (including SQL tasks, shell tasks, etc.).
Associated resource
Scheduling resources must be in the same region as EMR. After association, the project exclusively uses the associated resources. This list only displays scheduling resources not associated with other projects.
Integration Resources
Integration Resources
Integrated Resource Groups primarily execute DataInLong tasks.
Associated resource
After association, the project exclusively uses the associated resources. This list only displays integrated resources not associated with other projects.
Note:
WeData projects cannot be deleted once created.
Create Engine Mapping and add Sub-accounts to the project
1. Select the project, enter the Project Management Module.
2. In the Storage and Compute Engine Configuration, add Account Mapping for sub-accounts to bridge Tencent Cloud WeData accounts with EMR Engine accounts.
Note:
Sub-accounts to be mapped need to be created in the EMR engine beforehand, only then can the mapping be successfully added on the Tencent Cloud WeData platform.
3. Once Account Mapping addition is completed, select the Member Management menu, add sub-accounts as project members, and assign work roles.
Note:
Only sub-accounts that have successfully created Engine Mapping can be smoothly assigned project roles and given Security Policies for Permission Management.
Different roles focus on different aspects of work. WeData provides reasonable role positioning and clear permission control for different roles. Also, a member can be assigned multiple roles, helping tenants to efficiently and flexibly organize the division of labor among members to quickly engage in actual work. The roles are explained in the table below:
Roles
Description
Project Owner
The root account is by default the owner of the project, possessing all permissions of the project. The Project Owner role cannot be granted or revoked
Project Admin
The project management personnel, who have all the permissions of the project. They are primarily responsible for the maintenance and management of project information and project public resources; a project can have multiple management personnel, with the creator of the project being the default project owner
Data Engineer
Responsible for data development, analysis, etc., and has data development and operation and maintenance related operation permissions
Operations Engineer
Responsible for managing the task execution status in all production environments on the operation and maintenance page
Visitor management
Has read-only permission for all project information, and can inquire table data under the condition of obtaining authorization from the table owner
Note:
Each role's corresponding permissions are in continuous enrichment and improvement.
Yes
No
Was this page helpful?