JDBC V2 Connector > Mappings and elastic mappings in JDBC V2 Connector > JDBC V2 lookups in mappings and elastic mappings
  

JDBC V2 lookups in mappings and elastic mappings

In a mapping or an elastic mapping, you can configure a Lookup transformation to represent a JDBC V2 object.
Specify the name and description of the JDBC V2 lookup.
You can create the following lookups when you configure field mappings in a mapping or an elastic mapping task:
For more information about the Lookup transformation, see Transformations.
The following table describes the JDBC V2 lookup properties that you can configure in a Lookup transformation:
Property
Description
Connection Name
Name of the lookup connection.
Source Type
Source type. Select Single Object or Parameter.
Parameter
A parameter file where you define values that you want to update without having to edit the task.
Select an existing parameter for the lookup object or click New Parameter to define a new parameter for the lookup object.
The Parameter property appears only if you select parameter as the lookup type.
If you want to overwrite the parameter at runtime, select the Allow parameter to be overridden at run time option.
When the task runs, the Secure Agent uses the parameters from the file that you specify in the advanced session properties.
Lookup Object
Name of the lookup object for the mapping.
Multiple Matches
Behavior when the lookup condition returns multiple matches. Select from the following options:
  • - Return any row
  • - Return all rows
  • - Report error
Filter
Not applicable.
Sort
Not applicable.
The following table describes the JDBC V2 lookup advanced properties that you can configure in a Lookup transformation:
Advanced Source Property
Description
Pre SQL
The SQL query that the Secure Agent runs before reading data from the source.
Post SQL1
The SQL query that the Secure Agent runs after reading data from the source.
Fetch Size
The number of rows that the Secure Agent fetches from the database in a single call.
Table Name
Overrides the table name used in the metadata import with the table name that you specify.
Schema Name
Overrides the schema name of the source object.
If you specify the schema name both in the connection and the source properties, the Secure Agent uses the schema name specified in the source properties.
SQL Override
The SQL statement to override the default query and the object name that is used to read data from the JDBC V2 source.
1Applies only to mappings.
The remaining properties are applicable for both mappings and elastic mappings.