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 2019/04/29 16:02:21 UTC

[GitHub] [incubator-druid] gianm commented on issue #7439: API to drop and reload data by interval

gianm commented on issue #7439: API to drop and reload data by interval
URL: https://github.com/apache/incubator-druid/issues/7439#issuecomment-487639498
 
 
   > @leventov the drop API may not be idempotent between calls, if more segments get added to the same interval. And the reload API can have different outcomes based on the number of segments overshadowed in the interval at a time, so for same interval, reload API can mark different subset of segments as `used=true`. See the discussion [here](https://github.com/apache/incubator-druid/pull/7494#discussion_r277050169)
   
   Hmm this seems borderline to me. You can call the reload-by-interval API over and over and it is idempotent in the sense that it always takes the system to the 'all latest segments are marked used' state. But the specific segments may change from run to run and so the effects of the call may change from run to run.
   
   To me it's idempotent in the loose sense of 'nothing bad will happen if you call it repeatedly' but not in the strict sense of 'every call will have the same effect'.

----------------------------------------------------------------
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.
 
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