tImpalaOutput

Property type

• Either Built-in or Repository.

• Built-in: No property data stored centrally.

• Repository : Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.

Use an existing connection

Select this check box and in the Component List drop-down list, select the desired connection component to reuse the connection details you already defined.

Impala Driver

Select the driver you are using from the drop-down list.

Host

Database server IP address.

Port

Listening port number of DB server.

Database

Fill this field with the name of the database.

Additional JDBC Settings

Specify additional connection properties for the database connection you are creating.

This option is not available if you have selected the Use an existing connection check box in the Basic settings view.

Username and Password

Enter the database user authentication data to authenticate using LDAP.

To enter the password, click the […] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.

These parameters are not available when you select the Use kerberos authentication check box.

Use kerberos authentication

If you are accessing an Impala system running with Kerberos security, select this check box and then enter the Kerberos principal of this Impala system.

Schema and Edit Schema

• A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.

  Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • View schema: choose this option to view the schema only.

  • Change to built-in property: choose this option to change the schema to Built-in for local changes.

  • Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

    If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

• Built-in: The schema is created and stored locally for this component only. For more information about a component schema in its Basic settings tab, see Basic settings tab.

• Repository: The schema already exists and is stored in the Repository, hence can be reused. For more information about a component schema in its Basic settings tab, see Basic settings tab.

Table Name

Name of the table you need to write data in.

Action

Select whether you want to OVERWRITE the old data already existing in the destination or only APPEND the new data to the existing one.

Extended insert

Select this check box to combine multiple rows of data into one single INSERT action. This can speed up the insert operation.

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Global Variables

ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box.

A Flow variable functions during the execution of a component while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from it.

For more information about variables, see Using contexts and variables.

Usage rule

This component offers the benefit of flexible DB queries and covers all possible Impala SQL queries.