clintropolis commented on issue #18446: URL: https://github.com/apache/druid/issues/18446#issuecomment-3269087876
rather than a historical server level configuration, this feels like something that should be handled as part of load rules so that different strategies could be done on a per table basis, as tables can often have quite different usage patterns in some clusters, any reason I'm missing to not investigate extending load rules to also specify how segments are loaded? This is what I am planning to look into to extend the 'virtual storage' introduced in #18176, that is, extending load rules to allow specifying 'weak' loads so that whether or not to eagerly download segments from deep storage can be configured in a much more flexible manner instead of the 'all' or 'nothing' approach that the initial PR supports. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
