amrishlal commented on issue #7155: URL: https://github.com/apache/incubator-pinot/issues/7155#issuecomment-881222424
> Helix messaging server does take an async callback stub, which we can probably leverage to achieve that. async callback is what I was thinking about using. > Why gather responses? This is similar to our current segment reload message -- no response if one of the controllers fails to complete manually triggered periodic task successfully, then the user may want to know about that and hence the need for gathering responses. Also, user may want status information on when the periodictask was run last and what was the result of that run before deciding to trigger the periodictask manually again. Also it is interesting to note that PinotTaskManager (which is derived from ControllerPeriodTask) already seems to have an extensive set of controller apis (REST path "/tasks" through PinotTaskRestletResource) for adding/removing/deleting tasks and getting their status information, but "PeriodicTask" is a higher level construct, so I was thinking about adding another rest path "/periodictask" for triggering and getting status of PeriodicTask derived classes (excluding PinotTaskManager). Another option may be to deprecate current "/tasks" REST path and create "/periodictask" and "/periodictask/taskmanager" REST paths where the REST path "/periodictask/taskmanager" would be same as current "/tasks" REST path? -- 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]
