# tMysqlInput MapReduce properties

These properties are used to configure tMysqlInput running in the MapReduce Job framework.

The MapReduce tMysqlInput component belongs to the Databases family.

The component in this framework is available in all subscription-based Talend products with Big Data and Talend Data Fabric.

## Basic settings

| Property type | Either Built-In or Repository.<br><br><br>Built-In: No property data stored centrally.<br><br><br>Repository: Select the repository file where the<br>properties are stored. |
| --- | --- |
| ![](https://help.qlik.com/talend/en-US/components/7.2/Resources/images/Save_Icon.png) | Click this icon to open a database connection wizard and store the<br>database connection parameters you set in the component Basic settings view.<br><br>For more information about setting up and storing database connection<br>parameters, see *Talend Studio*<br>*User Guide*. |
| Use an existing connection | Select this check box and in the Component List click the relevant connection component to<br>reuse the connection details you already defined. |
| DB version | Select the version of the database to be used. |
| Host | Database server IP address. |
| Port | Listening port number of DB server. |
| Database | Name of the database. |
| Username and Password | DB user authentication data.<br><br>To enter the password, click the [...] button next to the<br>password field, and then in the pop-up dialog box enter the password between double quotes<br>and click OK to save the settings. |
| Schema and Edit<br>Schema | A schema is a row description. It defines the number of fields<br>(columns) to be processed and passed on to the next component. When you create a Spark<br>Job, avoid the reserved word line when naming the<br>fields. |
|  | Built-In: You create and store the schema locally for this component<br>only. |
|  | Repository: You have already created the schema and stored it in the<br>Repository. You can reuse it in various projects and Job designs. |
|  | Click Edit<br>schema to make changes to the schema. If the current schema is of the Repository type, three options are available:<br><br><ul> <li> <p> <span>View schema</span>: choose this                option to view the schema only.</p> </li> <li> <p> <span>Change to built-in property</span>:                choose this option to change the schema to <span>Built-in</span> for local changes.</p> </li> <li> <p> <span>Update repository connection</span>:                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 <span>No</span> upon completion and choose this schema metadata                again in the <span>Repository Content</span>                window.</p> </li> </ul> |
| Table<br>Name | Name of the table to be read. |
| Die on error | Select the check box to stop the execution of the Job when an error<br>occurs.<br><br>Clear the check box to skip any rows on error and complete the process for<br>error-free rows. When errors are skipped, you can collect the rows on error using a Row &gt; Reject link. |
| Query type and Query | Enter your DB query paying particularly attention to properly sequence<br>the fields in order to match the schema definition. |

## Usage

| **Usage rule** | In a<br>Talend<br>Map/Reduce Job, it is used as a start component and requires<br>a transformation component as output link. The other components used along with it must be<br>Map/Reduce components, too. They generate native Map/Reduce code that can be executed<br>directly in Hadoop.<br><br>You need to use the Hadoop Configuration tab in the<br>Run view to define the connection to a given Hadoop<br>distribution for the whole Job.<br><br>Note that in this documentation, unless otherwise<br>explicitly stated, a scenario presents only Standard Jobs,<br>that is to say traditional<br>Talend<br>data integration Jobs, and non Map/Reduce Jobs. |
| --- | --- |
| Hadoop Connection | You need to use the Hadoop Configuration tab in the<br>Run view to define the connection to a given Hadoop<br>distribution for the whole Job.<br><br>This connection is effective on a per-Job basis. |