# tImpalaRow Acts on the actual DB structure or on the data (although without handling data). The SQLBuilder tool helps you write your Impala SQL statements easily. tImpalaRow is the dedicated component for this database. It executes the Impala SQL query stated in the specified database. The Row suffix means the component implements a flow in the Job design although it does not provide output. This component is not shipped with your Talend Studio by default. You need to install it using the Feature Manager. For more information, see [Installing features using the Feature Manager](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/install-features-to-talend-studio). ## tImpalaRow Standard properties These properties are used to configure tImpalaRow running in the Standard Job framework. The Standard tImpalaRow component belongs to the Big Data family. The component in this framework is available in all Talend products with Big Data and in Talend Data Fabric. ## Basic settings | Properties | Description | | --- | --- | | 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.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels,
see [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | 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 | Enter 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 checkbox 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.

Either Built-in or Repository.
Built-in: Fill in manually the query statement or build it graphically using SQLBuilder
Repository: Select the relevant query stored in the Repository. The Query field gets accordingly filled in.

| | Guess Query | Click the Guess Query button to
generate the query which corresponds to your table schema in the
Query field. | | Query | Enter your DB query paying particularly attention to properly
sequence the fields in order to match the schema definition. | | Die on error | This check box is selected by default. Clear the check box to skip
the row on error and complete the process for error-free rows. If
needed, you can retrieve the rows on error via a Row > Rejects link. | ## Advanced settings | Properties | Description | | --- | --- | | Propagate QUERY's recordset | Select this check box to insert the result of the query into a
COLUMN of the current flow. Select this column from the use column list.

Information noteNote:

This option allows the component to have a different schema
from that of the preceding component. Moreover, the column that
holds the QUERY's recordset should be set to the type of
*Object* and this component
is usually followed by tParseRecordSet. | | tStatCatcher Statistics | Select this check box to collect log data at the component
level. | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | QUERY: the query statement
being processed. This is a Flow variable and it returns a string.

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 checkbox is
cleared, if the component has this checkbox.

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](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component offers the benefit of flexible DB queries and
covers all possible Impala SQL queries. |