Open ammar92 opened 10 months ago
I think for this we'd need to make changes to the sceduler API, as we currently ask the scheduler for those normalizer-jobs, and then when opening the submenu for a specific job, we ask octopoes for the yielded objects for that job. It would be good to have some knowledge of which jobs produced new objects, and which dind't in the scheduler for scheduling purposes.
We can add field (e.g. yielded objects) to the scheduler's NormalizerTask
. If the normalizer task runner knows what it has created it can update this field when updating the tasks status in the scheduler when finished. Otherwise, the scheduler needs to know about a finished event from the normalizer task runner in order to fill out the yielded objects field.
Is your feature request related to a problem? Please describe. The current design of the normalizer's tab on the tasks page sometimes makes it hard identifying normalizers that yield results. The existing setup has a dropdown button for each normalizer, making it somewhat cumbersome to locate those with actual yielded objects. This process involves multiple clicks and can be time-consuming or overwhelming when you have a big table with longer primary keys.
Describe the solution you'd like I wanted to propose the following enhancements: