chihsuan commented on PR #10879: URL: https://github.com/apache/ozone/pull/10879#issuecomment-5102888253
> Is there another call path where truncateTable operates on an existing populated DB? Otherwise, would it make more sense to remove the now-redundant truncate calls/helper instead? Thanks for checking! @echonesis Yes, I noticed the same and mentioned it on the Jira. Since HDDS-13553 the callers always get a fresh staged DB. I think it might still be worth fixing for future non-staged callers, and it's moving into `Table.clear()` as a general utility anyway. Removing the redundant calls is a fair point, but I'd prefer a separate Jira for that. -- 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]
