[Bug] [Seatunnel-web] Incorrect Task Instance Filter Options Displayed

[arshadmohammad]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

The current task instance filter options are as follows:
| 'SUBMITTED_SUCCESS'
| 'RUNNING_EXECUTION'
| 'READY_PAUSE'
| 'PAUSE'
| 'READY_STOP'
| 'STOP'
| 'FAILURE'
| 'SUCCESS'
| 'NEED_FAULT_TOLERANCE'
| 'KILL'
| 'WAITING_THREAD'
| 'WAITING_DEPEND'
| 'DELAY_EXECUTION'
| 'FORCED_SUCCESS'
| 'SERIAL_WAIT'
| 'DISPATCH'
| 'PAUSE_BY_ISOLATION'
| 'KILL_BY_ISOLATION'
| 'PAUSE_BY_CORONATION'
| 'FORBIDDEN_BY_CORONATION'

The updated job statuses are:
| 'INITIALIZING'
| 'CREATED'
| 'SCHEDULED'
| 'RUNNING'
| 'FAILING'
| 'FAILED'
| 'DOING_SAVEPOINT'
| 'SAVEPOINT_DONE'
| 'CANCELING'
| 'CANCELED'
| 'FINISHED'
| 'UNKNOWABLE'

Please update the job instance filter options to reflect the new job statuses.

SeaTunnel Version

seatunnel-web version 1.0.2

SeaTunnel Config

NA

Running Command

NA

Error Exception

No exception, only filter by state is not working

Zeta or Flink or Spark Version

No response

Java or Scala Version

No response

Screenshots

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[arshadmohammad]

If anyone is interested in working on this issue, please feel free to assign it to yourself.