[Feature]: Tables/Optimizing page display optimization

[baiyangtx]

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:

1. 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.
2. When querying Process details, use execution-id to query

In addition, this page has some additional optimization suggestions

1. Supports back-end paging query and filtering, and supports filtering by Type, ProcessId, and Status.
2. Support Process metadata dictionary, obtain the ProcessType enumeration and default query value supported by the current Table through the interface.
3. Donot dispay FinishTime due to already have a Duration fields

Use case/motivation

No response

Describe the solution

No response

Subtasks

No response

Related issues

No response

Are you willing to submit a PR?

• [ ] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[zhangmo8]

1

[github-actions[bot]]

This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occurs. To permanently prevent this issue from being considered stale, add the label 'not-stale', but commenting on the issue is preferred when possible.

[github-actions[bot]]

This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale'