walterddr opened a new issue #8091: URL: https://github.com/apache/pinot/issues/8091
Currently table is deleted first and the segments were deleted async behind the scene. however if the controller died during the async deletion and got restarted. User can call the API to create an exact same name table without any issue. This should not be allowed since there's still left-over segments. I am not sure what's the right way to fix it. but some thoughts: 1. create a soft delete state for a table marking it as deleting, and not allow same name table to be recreated until the segment deletion is done. 2. check the property store as well as table config store to make sure no left over segments exist, otherwise reject the table config creation request. Thoughts? -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
