itschrispeck commented on issue #11276: URL: https://github.com/apache/pinot/issues/11276#issuecomment-1672035813
> Support for quota for ingestion is best done through ingestion rate quota, which is already supported. Coupled with retention, this config can help determine how much data is stored for a table. I believe this is a different behavior. For our use case, we want to give tables a set storage quota as we are disk constrained. Ingestion increases are fine as long as long as we don’t store addition data overall. An ingestion rate quota would impact the freshness of our data > I guess the ask here is to introduce a size based retention manager in addition to the current time based. I feel this is doable. Essentially we remove segments until the storage quota is satisfied Yes, thanks for putting it so clearly -- 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
