Oozie supports providing default configuration for actions of a particular action type and default configuration for all actions
Oozie supports action configuration equivalent to the component's =*-site.xml= and =*.properties= files.
The configuration property in the oozie-site.xml is oozie.service.HadoopAccessorService.action.configurations and its value must follow the pattern [AUTHORITY=ACTION-CONF-DIR ,]*. Where AUTHORITY is the HOST:PORT of the Hadoop service (JobTracker/ResourceManager or HDFS). The ACTION-CONF-DIR is the action configuration directory. If the specified directory is a relative path, it will be looked under the Oozie configuration directory. An absolute path can also be specified. Oozie will load and process the action configuration files in the following order.
For example, for Hive action (which has the actionname defined as hive ), the list of files (under relevant ACTION-CONF-DIR ) processed would be,
Files processed earlier for an action have the lowest precedence and can have the configuration parameters redefined. All files and directories are relative to the ACTION-CONF-DIR directory.
In addition to explicit authorities, a '*' wildcard is supported. The configuration file associated with the wildcard will be used as default if there is no action configuration for the requested Hadoop service.
For example, the configuration in the oozie-site.xml would look like:
... <property> <name>oozie.service.HadoopAccessorService.action.configurations</name> <value>*=hadoop-conf,jt-bar:8021=bar-cluster,nn-bar:8020=bar-cluster</value> </property> ...
The action configuration files use the Hadoop configuration syntax.
By default Oozie does not define any default action configurations.