XBaith commented on code in PR #2859:
URL: https://github.com/apache/amoro/pull/2859#discussion_r1611092074
##########
docs/user-guides/using-tables.md:
##########
@@ -216,3 +216,37 @@ DROP TABLE test_db.test_log_store;
```
The current terminal is using the Spark engine to execute SQL. For more
information about deleting tables, you can refer to [Spark
DDL](../spark-ddl/#drop-table).
+
+## Explore table details
+The Amoro Tables details page provides multiple tabs to display the status of
the table from various dimensions, mainly including:
+
+| **Tab Name** | **Description**
|
+|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Details | Display the table's schema, primary key configuration,
partition configuration, properties; as well as the metric information of the
files stored in ChangeStore and BaseStore, including the number of files and
average file size, as well as the latest submission time of the files. |
+| Files | Display all partitions and files of the table.
|
+| Snapshots | Display all snapshots of the table, which can be filtered by
branch and tag.
|
+| Optimizing | Display all the self-optimizing processes of the table, each
record shows the number and average size of files before and after Optimize, as
well as the execution time of each process.
|
+| Operations | Display the current table's DDL historical change records.
|
+
+
+
+
+
+## Explore self-optimizing status
+The Optimizing page displays self-optimizing status of all tables.
+
+
+
+- **Optimizing Status**: The current optimizing status of the table, including
idle, pending, planning, minor, major, full, committing.
+ - idle: means that self-optimizing is not required on the table.
+ - pending: means that self-optimizing is required on the table and is
waiting for resources.
+ - planning: means that self-optimizing process is being planed.
+ - minor: means that minor optimizing is being executed on the table.
+ - major: means that major optimizing is being executed on the table.
+ - full: means that full optimizing is being executed on the table.
+ - committing: means that self-optimizing process is being committed.
+- **Duration**: The duration of the current status.
+- **File Count**: The total number of files involved in the current
Self-optimizing, including base, insert, eq-delete, and pos-delete file types.
+- **File Size**: The total size of files involved in the current
Self-optimizing.
Review Comment:
```suggestion
- **File Size**: The total size of files involved in the current
self-optimizing.
```
##########
docs/user-guides/using-tables.md:
##########
@@ -216,3 +216,37 @@ DROP TABLE test_db.test_log_store;
```
The current terminal is using the Spark engine to execute SQL. For more
information about deleting tables, you can refer to [Spark
DDL](../spark-ddl/#drop-table).
+
+## Explore table details
+The Amoro Tables details page provides multiple tabs to display the status of
the table from various dimensions, mainly including:
+
+| **Tab Name** | **Description**
|
+|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Details | Display the table's schema, primary key configuration,
partition configuration, properties; as well as the metric information of the
files stored in ChangeStore and BaseStore, including the number of files and
average file size, as well as the latest submission time of the files. |
+| Files | Display all partitions and files of the table.
|
+| Snapshots | Display all snapshots of the table, which can be filtered by
branch and tag.
|
+| Optimizing | Display all the self-optimizing processes of the table, each
record shows the number and average size of files before and after Optimize, as
well as the execution time of each process.
|
+| Operations | Display the current table's DDL historical change records.
|
+
+
+
+
+
+## Explore self-optimizing status
+The Optimizing page displays self-optimizing status of all tables.
+
+
+
+- **Optimizing Status**: The current optimizing status of the table, including
idle, pending, planning, minor, major, full, committing.
+ - idle: means that self-optimizing is not required on the table.
+ - pending: means that self-optimizing is required on the table and is
waiting for resources.
+ - planning: means that self-optimizing process is being planed.
+ - minor: means that minor optimizing is being executed on the table.
+ - major: means that major optimizing is being executed on the table.
+ - full: means that full optimizing is being executed on the table.
+ - committing: means that self-optimizing process is being committed.
+- **Duration**: The duration of the current status.
+- **File Count**: The total number of files involved in the current
Self-optimizing, including base, insert, eq-delete, and pos-delete file types.
Review Comment:
```suggestion
- **File Count**: The total number of files involved in the current
self-optimizing, including base, insert, eq-delete, and pos-delete file types.
```
##########
docs/user-guides/using-tables.md:
##########
@@ -216,3 +216,37 @@ DROP TABLE test_db.test_log_store;
```
The current terminal is using the Spark engine to execute SQL. For more
information about deleting tables, you can refer to [Spark
DDL](../spark-ddl/#drop-table).
+
+## Explore table details
+The Amoro Tables details page provides multiple tabs to display the status of
the table from various dimensions, mainly including:
+
+| **Tab Name** | **Description**
|
+|--------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Details | Display the table's schema, primary key configuration,
partition configuration, properties; as well as the metric information of the
files stored in ChangeStore and BaseStore, including the number of files and
average file size, as well as the latest submission time of the files. |
+| Files | Display all partitions and files of the table.
|
+| Snapshots | Display all snapshots of the table, which can be filtered by
branch and tag.
|
+| Optimizing | Display all the self-optimizing processes of the table, each
record shows the number and average size of files before and after Optimize, as
well as the execution time of each process.
|
+| Operations | Display the current table's DDL historical change records.
|
+
+
+
+
+
+## Explore self-optimizing status
+The Optimizing page displays self-optimizing status of all tables.
+
+
+
+- **Optimizing Status**: The current optimizing status of the table, including
idle, pending, planning, minor, major, full, committing.
+ - idle: means that self-optimizing is not required on the table.
+ - pending: means that self-optimizing is required on the table and is
waiting for resources.
+ - planning: means that self-optimizing process is being planed.
+ - minor: means that minor optimizing is being executed on the table.
+ - major: means that major optimizing is being executed on the table.
+ - full: means that full optimizing is being executed on the table.
+ - committing: means that self-optimizing process is being committed.
+- **Duration**: The duration of the current status.
+- **File Count**: The total number of files involved in the current
Self-optimizing, including base, insert, eq-delete, and pos-delete file types.
Review Comment:
Should we describe it in more detail? For example with a self-optimising
process?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
