shounakmk219 opened a new pull request, #16977:
URL: https://github.com/apache/pinot/pull/16977

   ## Description
   
   When minion tasks are scheduled with the /schedule endpoint without 
specifying a particular table it schedules the tasks for all tables where the 
task is configured. This leads to controller submitting a single job containing 
task configs from multiple tables. When user opens the minion UI it gets 
confusing as subtasks from different tables appears on the UI making it hard to 
follow the actual progress for the particular table
   
   ### Current behaviour
   
   The test1 table view shows 30 subtasks (only 15 subtasks belong to the table)
   <img width="1726" height="891" alt="image" 
src="https://github.com/user-attachments/assets/81585b60-31b1-4042-aaf9-fd4cedf12648";
 />
   
   One of the subtask from another table (test2)
   
   <img width="3452" height="1628" alt="image" 
src="https://github.com/user-attachments/assets/035affed-d4ba-4fe9-b7b4-284c3e5f2358";
 />
   
   
   ### After the changes
   
   Post the table based filtering each table view will only list the subtasks 
that belong to the table (check the subtask count showing 15 now) 
   
   <img width="1726" height="891" alt="image" 
src="https://github.com/user-attachments/assets/c813a9b5-a090-4752-89e4-f7bae371d0bc";
 />
   
   ### Important changes
   
   - New query param `tableName` added to `/tasks/task/{taskName}/debug` 
endpoint to filter based in table name. Subtasks from all tables would be 
returned if table name is not passed (current behaviour)
   - Updated minion task manager UI page to pass the tableName filter param to 
show the correct view
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to