The Tables/Optimizing page should display the execution status of the Table Maintenance Process on the table.
By default, each row of records corresponds to an Execution.
The current Process API design cannot reflect the process of multiple retries of a Process. This is because Amoro currently only has Task-level retries and does not have the concept of Process-level retries.
In order to display the process being executed multiple times on the page without making major modifications to the front-end framework, here are the following suggestions:
Add an additional execution-id to the current process data structure. This column will not be displayed. At the same time, the process id displayed on the frontend will be repeated.
When querying Process details, use execution-id to query
In addition, this page has some additional optimization suggestions
Supports back-end paging query and filtering, and supports filtering by Type, ProcessId, and Status.
Support Process metadata dictionary, obtain the ProcessType enumeration and default query value supported by the current Table through the interface.
Donot dispay FinishTime due to already have a Duration fields
zhangmo8
commented
2 weeks ago
Description
The Tables/Optimizing page should display the execution status of the Table Maintenance Process on the table. By default, each row of records corresponds to an Execution.
The current Process API design cannot reflect the process of multiple retries of a Process. This is because Amoro currently only has Task-level retries and does not have the concept of Process-level retries.
In order to display the process being executed multiple times on the page without making major modifications to the front-end framework, here are the following suggestions:
In addition, this page has some additional optimization suggestions
Use case/motivation
No response
Describe the solution
No response
Subtasks
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct