Jackie-Jiang commented on issue #6679: URL: https://github.com/apache/pinot/issues/6679#issuecomment-999073958
I think here is what we have agreed on: - Create a new rest API on controller to fix the partition without consuming segment - The API takes the table name, optional partition group id (if not provided, apply to all partitions) I feel the offset strategy might not be needed because that can only be applied to new partition where no segment exists, which is handled in the periodic check. In order to skip a bad offset, the API can take an optional parameter to use the LATEST offset for the new consuming segment. I do suggest allowing users to put an offset if they know where to consume for the new consuming segment, but this can be done as the second step. @mcvsubbu What do you think? -- 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]
