klsince commented on issue #7320: URL: https://github.com/apache/pinot/issues/7320#issuecomment-901487852
Is 're-push of segment' the feature described in this issue https://github.com/apache/pinot/issues/7321? In fact, as followups from the incident, we planned these two options: 1) add option to force segment download (mainly for mitigation); 2) enable index cleanup for V3 format, so that indices on servers stay in sync with what's set in table config not just when adding new ones but also when removing old ones. In general, re-push of segment is kinda heavy lifting for index cleanup particularly for large table, as it incurs considerable network egress cost while downloading large volume of data. Besides, letting indices on servers stay in sync with what's set in table config makes it a bit more intuitive to use Pinot, basically deleting indices would reduce disk usage. -- 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]
