[GitHub] [helix] narendly commented on issue #2024: Are all resources expected to have ResourceConfig?

[GitBox <gi...@apache.org>]

narendly commented on issue #2024:
URL: https://github.com/apache/helix/issues/2024#issuecomment-1092885415

   Hi @hmhagberg - thank you for the question. The historical context is this: IdealState is the de-facto definition for a resource with its required fields, but applications wanted to add more application-specific configs. But the original intention was to make IdealStates immutable (not enforced, unfortunately), so Helix added support for ResourceConfig. This is why things can work without ResourceConfig, but the intention is for a given resource to have a ResourceConfig and an IdealState pair.
   
   But the log message seems to be coming from ConfigAccessor, which is entirely used by the application logic. Are you trying to ConfigAccessor#get? This, I don't believe, is being called by the Helix controller pipeline.


-- 
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: reviews-unsubscribe@helix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@helix.apache.org
For additional commands, e-mail: reviews-help@helix.apache.org