Hi, Based on recent discussions, we have arrived at a reasonable design for the hierarchy of Helix entities and their assorted configurations. If a property is configurable (e.g. the rebalance mode of a resource), it is part of a configuration, otherwise it is only part of the top level entity (e.g. the external view of a resource. We also plan to incorporate the concept of a user config, which consists of parameters that a user can understand, as could be the case in a rebalance task, but are not understandable to Helix. The full hierarchy of the entities and their configs can be found at: https://cwiki.apache.org/confluence/download/attachments/34014947/config_hierarchy.png
Thanks, Kanak
