You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2018/10/11 06:53:36 UTC

[GitHub] licl2014 edited a comment on issue #6387: Druid load rule based on start date of segments

licl2014 edited a comment on issue #6387: Druid load rule based on start date of segments
URL: https://github.com/apache/incubator-druid/issues/6387#issuecomment-428837855
 
 
   Yep, we have same problem, our scenarios like the following:
   1. I have load rules like: load 3 days, drop forever.
   2. (today is 2018-10-11)My datasource has 4 days data and merged into one segment from **2018-10-08 to 2018-10-12**.
   4. Because of the rule, the coordinator will drop that segment, in fact , we only want drop the data from **2018-10-08 to 2018-10-09**.
   
   The related code in PeriodLoadRule.java is **currInterval.overlaps(intervial) && interval.getStartMillis() >= currInterval.getStartMillis()**, here ,   currInterval is **"2018-10-09/2018-10-12"**,  interval is **"2018-10-08/2018-10-12"**, "currInterval.overlaps(intervial)" is **true** and "interval.getStartMillis() >= currInterval.getStartMillis()" is **false**.  @jihoonson @QiuMM 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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