Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
When upgrading a custom service that has new dictionaryName, the database startup checks fail because it doesn't find the new properties in the current config version.
Two options for a workaround include, uninstalling/reinstalling the service or manually creating the missing properties in Ambari before upgrading.
It would be helpful if there was a way to update the existing configuration on startup.