DataWorks:MaxCompute table data

On the table details page, you can view information such as the Number Of Views, Number Of Reads, and Number Of Favorites in the Table Basic Information area on the left.

• Views: The number of times the table details page was viewed in Data Map over the last 30 days. This data is collected offline and has a T+1 day latency.

• Reads: The number of tasks that read the MaxCompute table from the production environment in the last 30 days. Task types include SQL, Tunnel Download, Data Integration, and DataService Studio APIs. Only the number of reads for tasks associated with scheduling is counted. Reads from tasks outside of DataWorks are not counted. This data is collected offline and has a T+1 day latency.

• Favorites: The number of users who added the table to their favorites. This data is collected in real time.

• Storage: The logical storage size of the table. This data is collected offline and has a T+1 day latency.

• Health Score: The table's rating in Data Health > Data Governance > Governance Health Score. You can use this score to determine whether the table requires governance.

• Output Task: The ID of the DataWorks recurring schedule task that writes to the current table. If the table is periodically updated but no task ID is displayed, it may be because the table is written to by a task that is not a DataWorks recurring schedule task. Contact the table owner for details. This data is collected offline and has a T+1 day latency.

  Note

  If you do not have permission to view the code of the output task, contact the administrator of the workspace where the task is located to grant you the required permissions. For more information, see Enable code and log isolation.

Click Details to view the table's Field Information, Partition Information, and Change Records.

• Field information

  You can view the table's field information. If the table is a partitioned table, you can also view the Partition Field Information.

  Operation	Description
  Edit	Click to edit the field's Description, Business Description, Security Level, and Primary Key. Then, Save or Cancel your changes. You can also select multiple fields to set their security level in a batch. Note Only a Workspace Administrator or the table owner can edit table fields. To allow another user to edit table fields, grant the user the Workspace Administrator role. For more information, see Manage permissions on global-level modules. The Security Level column is displayed only for tables for which field security levels are individually set. You can set security levels for table fields here only after you enable the field security level feature in the MaxCompute engine. For more information about how to enable the security level feature, see Label-based access control.
  Batch Edit Security Level	Set security levels for multiple table fields in a batch to improve data security.
  Upload	Click and drag the local data that you want to upload to the Batch Upload Field Information dialog box. Note Only a Workspace Administrator or the table owner can upload data to the target table. To allow another user to upload data, grant the user the Workspace Administrator role. For more information, see Manage permissions on global-level modules. Only .xlsx files (Excel 2007) are supported. You can also Download A Template File. This feature is not supported for model tables generated by smart modeling.
  Download	Downloads the field information for the current table.
  Generate Select	After you click this option, you can view or Copy the select statement for the current table in the Generate Select Statement dialog box.
  Generate DDL	Click to view or Copy the table creation statement in the Generate DDL Statement dialog box.

  Note

  • Field popularity: This metric indicates the number of times the field was used in a join operation on the previous day. This number is converted to a star rating. The highest rating is five stars and the lowest is zero stars.

  • Associated metric: Displays the model metrics associated with the field. To create or update an association, go to the dimensional modeling page. On the editing page for the target table, manage the association between fields and metrics in the field management section. After you publish the model table, the association takes effect.

• Partition information

  You can view the partition information of the current table, such as the Partition Name, Number Of Records, and Logical Storage Size.

  Note

  • The number of partition records and size are for reference only. Data updates may be delayed. The data on the engine side is the most accurate.

  • For a MaxCompute Transactional table, the Number Of Records cannot be viewed and is fixed at -1. To obtain the number of records, run the SELECT COUNT(*) FROM <table_name> WHERE <partition>; command.

• Change records

  You can view the change records of the current table, such as the Change Description, Change Type, and Granularity.

  In the upper-left corner of the Change Records tab, you can select a change type from the drop-down list to view the corresponding change records.

Lineage information shows the relationships between tables and between fields. It is derived by parsing the actual data forwarding from operations such as recurring schedules and data synchronization. On the lineage information page, you can view the upstream and downstream of a table or field. You can also view the source of the table's raw data and the destination database to which the table data is forwarded. You can also perform an impact analysis for different lineage levels.

• View table lineage

  On the Table Lineage tab, you can view the lineage details of the current table. This includes:

  • You can view the number of upstream and downstream nodes for each node in the current table lineage. Hover over a table or task type to view its basic information, logs, and code.

  • Enter a keyword in the search box of the lineage graph to display all downstream nodes of the current table that contain the keyword. You can also enter @+account_name to display all downstream nodes of the current table that belong to the specified account.

  • Click or in the lineage graph to expand or collapse the corresponding upstream and downstream nodes.

• View field lineage

  On the Field Lineage tab, you can view the lineage details of the target field. This includes:

  • In the Switch Field area, you can switch the field in the current table to view the corresponding field lineage graph.

  • You can view the number of upstream and downstream nodes for each node in the current field lineage. Hover over a field or task type to view its basic information, logs, and code.

  • Enter a keyword in the search box of the lineage graph to display all downstream nodes of the current field that contain the keyword. You can also enter @+account_name to display all downstream nodes of the current field that belong to the specified account.

  • Click or in the lineage graph to expand or collapse the corresponding upstream and downstream nodes.

• Impact analysis

  If the table schema or data of the current table changes, all downstream nodes are affected. You can use the Impact Analysis feature to identify which downstream tables exist and predict which tables may be affected by a change. On this page, you can filter by lineage level, task type, and table type to display the downstream tables that meet the specified conditions within the analyzed lineage level. You can also download the analysis results.

  Note

  You can analyze up to 50 levels of table lineage.

You can view the table's Usage Records from the Frequent Associations and Access Statistics dimensions.

• Frequent Associations: Shows the number of users who are using the current table data.

  Note

  This counts the number of times the table was used as a join condition in the last 30 days. This data is collected offline and has a T+1 day latency.

• Access Statistics: Displays the table's usage records in charts.

  • Read Trend Chart: The line chart shows the number of reads per day, distinguishing between reads from the development and production environments. The number of field associations is related to the number of task executions and the number of times the field appears in the code. This data is collected offline and has a T+1 day latency.

    For example, if a field appears once in a task and the task is executed twice, the count is two. If a field appears twice in the code, a single task run results in a field count of two.

  • Field References In Clauses: Shows statistics on the number of times a field is used in SQL clauses, such as `where`, `select`, `join`, and `groupBy`. This data is collected offline and has a T+1 day latency.

  • Top Readers: Shows statistics on the users who read the table in SQL in the last 30 days. This includes access by tenant accounts used for scheduling and individual accounts. The read operations include using fields in `where`, `select`, `join`, and `group by` clauses. This data is collected offline and has a T+1 day latency.

You can view data governance details to quickly see the table's governance health score, the trend of issues that require governance, and the specific governance items. You can also quickly resolve the issues that require governance.

• Health Score: A quantitative assessment of the table's assets in five health domains: storage, computing, development, quality, and security. The health score reflects the effectiveness of governance. A higher score indicates better governance.

• Trend Of Issues To Be Governed: Shows the historical trend of the number of issues that require governance, which helps you better understand the table's governance history.

• Governance Items: Shows the current list of issues that require governance. You can click an issue name in the Governance Item column or the button in the Actions column to go to Data Asset Governance > Overview > Governance Items to handle governance items.