vogievetsky commented on issue #14330:
URL: https://github.com/apache/druid/issues/14330#issuecomment-1559895699
Overall I really like the design.
Some thoughts and questions:
- Will there be an API to fetch all the storage policies together? The
equivalent of `GET /druid/coordinator/v1/rules` that is needed for the console.
- Like Gian I want to know what will actually be stored in the DB? Will
setting a storagePolicy actually just write some new load rules that I will be
able to see if I query the load rules directly? What if I set a storagePolicy
and then write a load rule will it effectively "update" the storage policy? I
am 👍 for an approach where this is all just sugar on top of existing load rules
and the storage policy is not a real object that is stored.
- `Disallow retain if auto-kill configuration is disabled` I have issues
with that. What if you set retain and then disable the auto-kill. How will the
UI know if auto-kill is enabled or not (so as to know to render the `retain`
controls or not)
- What is going on here:
<img width="765" alt="image"
src="https://github.com/apache/druid/assets/177816/723dbcc5-9d69-4146-ad12-583b864c7ceb";>
What happens if `hot` is not set is everything hot or nothing is hot? I
think the load rule part of the example suggests that everything is hot?
- What would the storage policy for the current default of everything is hot
look like?
--
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]
