saurabhd336 commented on PR #8663: URL: https://github.com/apache/pinot/pull/8663#issuecomment-1123200743
@sajjad-moradi I had a discussion with @npawar on this, and seems like this functionality addresses issues arising due to accidental deletion of consuming segments, and therefore its availability is of importance, beyond the Pause / Resume feature too. From the Pause / Resume design doc's perspective, I see this API fitting the Resume API description fairly well and the "in one Ideal State update operation, sets the “isTablePaused” flag to false" operation can be added to this, optionally if the table is indeed paused? Do you see any challenges with that? Are we saying we'd need to write the resume API from scratch when implementing the Pause / Resume feature? cc: @npawar for comments -- 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]
