mcvsubbu commented on pull request #8176: URL: https://github.com/apache/pinot/pull/8176#issuecomment-1034000370
This PR is complicating things and trying to solve a problem that may never exist. It is fair to NOT expect that deletion of a table behave as per table config settings. it is ok to use the cluster behavior if the table config is not found. If it is desired that the segments be re-loaded onto another table, the operator should save the segments before creating a new table. Also, I don't understand the need to re-scan all segments when table config retention time is changed. -- 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
