gianm commented on issue #14330: URL: https://github.com/apache/druid/issues/14330#issuecomment-1559830650
Some initial thoughts: From the "operational impact" section, it sounds like there is no storage as part of this proposal, just syntax sugar on load/drop rules. Is this correct? If so: - what happens on `GET` if there are some load/drop rules for a datasource that can't be mapped onto a storage policy object? Or, is it possible for all combinations of load/drop rules to be mapped onto storage policy? - how are the cluster-wide default load/drop rules dealt with? Additionally, did you consider options where the storage policy _is_ a real object that is stored, perhaps in the new (& currently not-really-used) catalog? In that case the API would be through `CatalogResource`. Curious what you see as the pros and cons of these two approaches. -- 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]
