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/07/23 15:44:30 UTC
[GitHub] [incubator-druid] leventov commented on issue #8125: Leave a single
CachePopulator and choose sync/async mode automatically
leventov commented on issue #8125: Leave a single CachePopulator and choose sync/async mode automatically
URL: https://github.com/apache/incubator-druid/issues/8125#issuecomment-514267788
> And is it a good idea to have background cache population be a generic thing at all? What if we only had foreground population and left it up to the individual Cache impls to do background pushing to remote cache servers if they want to?
This is very similar to the automatic sync/async choice that I suggested. It makes sense to me, too.
----------------------------------------------------------------
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