Hive Action Parameters
Following are descriptions and examples for the parameters you can set in the Hive action node.
Use of Credentials and SLA can be set in the Hive action, but the configuration for them is done from the global Settings menu.
Table 7.1. Hive Action, General Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Hive Option | The options are Script or Query. | You can run the Hive action using a script or by entering a query in HiveQL. | |
| Script | Navigate to the HDFS location of the script containing the Hive queries. | You can bundle Hive queries together in a script for faster execution. |
/user/ambari-qa/processworkflow/queries/create_drivers.hql |
| Query | You can enter HiveQL commands instead of using a script to request and retrieve data. | See the Apache documentation for more information. |
create table temp_drivers (col_value STRING); LOAD DATA INPATH |
| Job XML | You can select one or more job.xml files to pass Hive configuration details. | The configuration file that specifies the variables used in the workflow that allow Hive to communicate with the metastore. Can be overwritten or replaced by entries under the Configuration section. | hive-conf.xml |
| Param | Use to pass the values of variables referenced in the script or HiveQL. | See the Apache documentation for more information. |
If hive query is: select * from table where joindate=${joinDate} Param should be: <param>joinDate=13-11-15</param> |
Table 7.2. Hive Action, Transition Parameters
| Parameter Name | Description | Additional Information | Default Setting |
|---|---|---|---|
| Error To | Indicates what action to take if the action errors out. | You can modify this setting in the dialog box or by modifying the workflow graph. | Defaults to kill node, but can be changed. |
| OK To | Indicates what node to transition to if the action succeeds. | You can modify this setting in the dialog box or by modifying the workflow graph. | Defaults to the next node in the workflow. |
Table 7.3. Hive Action, Advanced Properties Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Resource Manager | Master node that arbitrates all the available cluster resources among the competing applications. | The default setting is discovered from the cluster configuration. | ${resourceManager} |
| Name Node | Manages the file system metadata. | Keeps the directory tree of all files in the file system, and tracks where across the cluster the file data is kept. Clients contact NameNode for file metadata or file modifications. | ${nameNode} |
| File | Select any files that you want to make available to the Hive action when the workflow runs. | MySQL data files | |
| Archive | Select any archives that you want to make available to the Hive action when the workflow runs. | archived data files | |
| Prepare | Select mkdir or delete and identify any HDFS paths to create or delete before starting the job. | Use delete to do file cleanup prior to job execution. Enables Oozie to retry a job if there is a transient failure (the job output directory must not exist prior to job start). If the path is to a directory: delete deletes all content recursively and then deletes the directory. mkdir creates all missing directories in the path. | |
| Arg | Identify any arguments to be passed to the Hive script. |
Table 7.4. Hive Action, Configuration Parameters
| Parameter Name | Description | Additional Information | Example |
|---|---|---|---|
| Name and Value | The name/value pair can be used instead of a job.xml file or can override parameters set in the job.xml file. |
Used to specify formal parameters. If the name and value are specified, the user can override the values from the Submit dialog box. Can be parameterized (templatized) using EL expressions. See the Apache documentation for more information. |