All Products
Search
Document Center

DataWorks:Data governance FAQ

Last Updated:Jun 20, 2026

This topic addresses common issues related to data governance in DataWorks.

Question categories

Storage discrepancy in Data Map

The storage amount is a real-time value, while the storage trend chart displays a point-in-time snapshot. A discrepancy between these two values is expected, especially if your current computing workload is low and generates few temporary tables.

New table not found in Data Map

If the status of a table in Data Map is inconsistent with its actual state, you can use the Manual Sync Table feature to synchronize the table to its latest state. This issue can occur in the following scenarios:

  • The table schema is not updated in Data Map.

  • A new table cannot be found in Data Map.

  • A new table cannot be found in Data Integration.

In the top navigation bar, click My Data. In the left-side navigation pane, choose My Tools > Manual Sync Table. In the Table GUID field, enter the GUID of the target table, prefixed with odps., and then click Manual Sync.

Notifying downstream of logic changes

You can notify relevant downstream owners by email in bulk in the Lineage > Impact Analysis section on the Data Map Table Details page.

Hive tables supporting data preview

Data preview is supported only for specific types of Hive tables in E-MapReduce (EMR). If you cannot preview data from a Hive table, contact the cluster administrator to verify that your configuration meets the requirements in the following table.

Note

In the table, 支持 indicates that data preview is supported, and 不支持 indicates that it is not supported.

EMR cluster type

Metastore type

Storage type: OSS

Storage type: OSS-HDFS

Storage type: HDFS

Data Lake cluster (DataLake)

Data Lake Formation (DLF)

支持

支持

不支持

RDS instance

支持

支持

支持

MySQL

支持

支持

支持

custom cluster (Custom)

Data Lake Formation (DLF)

支持

支持

不支持

RDS instance

支持

支持

支持

MySQL

支持

支持

支持

Other clusters

--

不支持

Inconsistent masking in Data Security Guard

Data masking triggers only when at least 80% of the data matches a specified rule.