The components defined in the metainfo.xml of the current service are merged with those of the parent (supports delete). The configuration dependencies defined in the metainfo.xml of the current service version are merged with those of the parent service version. The custom commands defined in the metainfo.xml of the current service version are merged with those of the parent service version. If the `supports_do_not_extend` attribute is specified as `true`, the configuration type will not be merged.īy default all attributes of the service and components if defined in the metainfo.xml of the current service version will replace those of the parent service version unless specified in the sections that follow. Configuration files defined at any level can be omitted from the services configurations by specifying the config-type in the excluded-config-types list: įor an individual configuration file (or configuration type) like core-site.xml, it will by default merge with the configuration type from the parent. The configurations directory in the current service version merges the configuration files with those from the parent service version. You will need to copy all the files you wish to keep from that directory structure.
This means the files included in those directories at the parent level will not be inherited. The following directories if defined in the current service version replace those from the parent service version: The following files if defined in the current service version are merged with the parent service version (supports removing/deleting parent entries): Note: All the services' role command orders will be merge with the stack's role command order to provide a master list. So that Ambari web UI can calculate quick link URLs based on the information and populate the quicklinks drop-down list accordingly. Ambari server parses the quicklink JSON file and provides its content to the UI. The following files if defined in the current service version replace the definitions from the parent service version: A service can add a list of quick links to the Ambari web UI by adding metainfo to a text file following a predefined JSON format. When a service inherits from another service version, how its defining files and directories are inherited follows a number of different patterns. A service can inherit through the stack but may also inherit directly from common-services.
0 kommentar(er)
