Help Center> DataArts Studio> Service Overview> Constraints and Restrictions
Updated on 2024-04-03 GMT+08:00

Constraints and Restrictions

Browser Restrictions

The following table lists the recommended browser for logging in to DataArts Studio.
Table 1 Browser compatibility

Browser

Recommended Version

Recommended OS

Remarks

Google Chrome

115, 114, and 113

Windows 10

The resolution ranges from 1366x768 px to 1920x1080 px. 1920x1080 px is the optimal resolution for the best display of the console.

Use Restrictions

Before using DataArts Studio, you must read and understand the following restrictions:
Table 2 Restrictions for using DataArts Studio

Component

Restriction

Public

  1. DataArts Studio must be deployed based on HUAWEI CLOUD. If resources are isolated, DataArts Studio can be deployed in a full-stack DeC. In addition, DataArts Studio can be deployed on Huawei Cloud Stack or Huawei Cloud Stack Online.

    For more information about the application scenarios and differences between the full-stack DeC, Huawei Cloud Stack, and Huawei Cloud Stack Online, contact sales.

  2. DataArts Studio is a one-stop platform that provides data integration, development, and governance capabilities. DataArts Studio has no storage or computing capability and relies on the data lake base.
  3. Only one DataArts Studio instance can be bound to an enterprise project. If an enterprise project already has an instance, no more instance can be added.
  4. Different components of DataArts Studio support different data sources. You need to select a data lake foundation based on your service requirements. For details about the data lakes supported by DataArts Studio, see Data Sources Supported by DataArts Studio.

Management Center

  1. Due to the constraints of Management Center, other components (such as DataArts Architecture, DataArts Quality, and DataArts Catalog) do not support databases or tables whose names contain Chinese characters or periods (.).
  2. The free CDM cluster provided by a DataArts Studio instance has limited specifications. You are advised to use it only as an agent for a data connection in Management Center.
  3. You are advised to use different CDM clusters for a data connection agent in Management Center and a CDM migration job. If an agent and CDM job use the same cluster, they may contend for resources during peak hours, resulting in service unavailability.
  4. If a CDM cluster functions as the agent for a data connection in Management Center, the cluster cannot connect to multiple MRS security clusters. You are advised to plan multiple agents which are mapped to MRS security clusters one by one.
  5. If a CDM cluster functions as the agent for a data connection in Management Center, the cluster supports a maximum of 200 concurrent active threads. If multiple data connections share an agent, a maximum of 200 SQL, Shell, and Python scripts submitted through the connections can run concurrently. Excess tasks will be queued. You are advised to plan multiple agents based on the workload.

  6. A maximum of 200 data connections can be created in a workspace.
  7. The concurrency restriction for APIs in Management Center is 100 QPS.

DataArts Migration

  1. You can enable automatic backup and restoration of CDM jobs. Backups of CDM jobs are stored in OBS buckets. For details, see Automatic Backup and Restoration of CDM Jobs.
  2. The DataArts Migration cluster is deployed in standalone mode. A cluster fault may cause service and data loss. You are advised to use the CDM Job node of DataArts Factory to invoke CDM jobs and select two CDM clusters to improve reliability. For details, see CDM Job.

For more constraints on DataArts Migration, see CDM Constraints.

DataArts Factory

  1. You can enable backup of assets such as scripts and jobs to OBS buckets. For details, see Managing Backups.
  2. A maximum of 10,000 jobs can be created in a workspace.
  3. A maximum of 1,000 execution results can be displayed for RDS SQL, DWS SQL, Hive SQL, DLI SQL, and Spark SQL scripts, and the data volume is less than 3 MB. If the number of execution results exceeds 1,000, you can dump them. A maximum of 10,000 execution results can be dumped.

DataArts Architecture

  1. DataArts Architecture supports ER modeling and dimensional modeling (only star models).
  2. The maximum size of a file to be imported is 4 MB. A maximum of 3,000 metrics can be imported. A maximum of 500 tables can be exported at a time.
  3. The quotas for the objects in a workspace are as follows:
    • Subjects: 5,000
    • Data standard directories: 500; data standards: 20,000
    • Atomic, derivative, and compound metrics: 5,000 for each
  4. The quotas for different custom objects are as follows:
    • Custom subjects: 10
    • Custom tables: 30
    • Custom attributes: 10
    • Custom business metrics: 50

DataArts Quality

  1. The execution duration of data quality jobs depends on the data engine. If the data engine does not have sufficient resources, the execution of data quality jobs may be slow.
  2. A maximum of 50 rules can be configured for a data quality job. If necessary, you can create multiple quality jobs.

DataArts Catalog

  1. Metadata collection tasks can be obtained through DDL SQL statements of the engine. You are not advised to collect more than 1,000 tables through a single task. If necessary, you can create multiple collection tasks. In addition, you need to set the scheduling time and frequency properly based on your requirements to avoid heavy access and connection pressure on the engine. The recommended settings are as follows:
    • If your service requires a metadata validity period of one day, set the scheduling period to max(one day, one-off collection period). This rule also applies to other scenarios.
    • If your service mainly runs in the daytime, set a scheduling time in the night during which the metadata collection has the minimum impact on the data source. This rule also applies to other scenarios.
  2. Only the jobs that are scheduled and executed in DataArts Factory generate data lineages. Tested jobs do not generate data lineages.

DataArts DataService

  1. The shared edition is designed only for development and testing. You are advised to use the exclusive edition which is superior to the shared edition.
  2. DataArts DataService clusters are bound to workspaces. After a cluster is created, its specifications cannot be modified, and its edition cannot be upgraded.