[GitHub] [druid] FrankChen021 commented on issue #13080: PeriodLoadRule cannot Remove expired segment

[GitBox <gi...@apache.org>]

FrankChen021 commented on issue #13080:
URL: https://github.com/apache/druid/issues/13080#issuecomment-1249111218

   I think @kfaraz 's answer makes sense.
   
   Actually, our [doc](https://druid.apache.org/docs/latest/operations/rule-configuration.html#load-rules) has pointed out this:
   
   > Load rules indicate how many replicas of a segment should exist in a server tier. Please note: If a Load rule is used to retain only data from a certain interval or period, it must be accompanied by a Drop rule. If a Drop rule is not included, data not within the specified interval or period will be retained by the default rule (loadForever).
   
   Although we have doc to state this, I think current default rule(loadForever) is little bit counterintuitive. 
   Maybe the default rule should be `dropForever`? But because Druid provides flexible retention rules(both load and drop), chaning the default rule to `dropForever` might not be so easy. 
   
   In constrast to Druid, some other DBs, only provides load rules(not the same concept, but similiar to Druid's load rule), so it makes sense that its default behaviour is a `dropForever` rule.
   
   


-- 
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-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org