- Data Map
- Why is the value of the Storage parameter quite different from the statistics shown in the storage trend chart on the Overview page of Data Map?
- Why does Data Map not display the real-time lineage information?
- What do I do if no search results are returned when I search for a new table in Data Map?
- How do I notify the owners of descendant nodes of the changes to the business logic?
- Which types of Hive tables can be previewed in Data Map?
- Data Security Guard
Why is the value of the Storage parameter quite different from the statistics shown in the storage trend chart on the Overview page of Data Map?
The value of the Storage parameter is updated in real time, while the storage trend chart displays the storage statistics at specific points in time. If a small number of temporary tables are generated after a specific point in time, the statistics at the specific point in time in the storage trend chart may be inconsistent with the value of the Storage parameter.
Why does Data Map not display the real-time lineage information?
The lineage information is updated with a latency of at least one day.
What do I do if no search results are returned when I search for a new table in Data Map?
You can use the manual synchronization feature in Data Map if the new table cannot be found in Data Map or the data of the table is inconsistent with that in Data Map. Manual synchronization is required in the following scenarios:
- The schema changes of the tables in the Workspace Tables pane are not updated to Data Map.
- No search results are returned when you search for a new table in Data Map.
- No search results are returned when you search for a new table in Data Integration.
How do I notify the owners of descendant nodes of the changes to the business logic?
Which types of Hive tables can be previewed in Data Map?
EMR cluster type | Metadata storage type | Data storage type: OSS | Data storage type: OSS-HDFS | Data storage type: HDFS |
---|---|---|---|---|
DataLake clusters | Data Lake Formation (DLF) | |||
RDS instance | ||||
MySQL | ||||
Custom clusters | DLF | |||
RDS instance | ||||
MySQL | ||||
Other clusters | -- |
Why does the de-identification feature fail to take effect for the query results sometimes after I configure de-identification rules in Data Security Guard?
The de-identification feature works only if 80% of the records that are queried match the de-identification rules.