|
Component family
|
Databases/VectorWise
|
|
|
Function
|
tVectorWiseRow is the specific
component for this database query. It executes the SQL query stated
in the specified database. The row suffix means the component
implements a flow in the job design although it doesn’t provide
output.
|
|
Purpose
|
Depending on the nature of the query and the database, tVectorWiseRow acts on the actual DB
structure or on the data (although without handling data). The
SQLBuilder tool helps you write your SQL statements easily.
|
|
Basic settings
|
Property type
|
Either Built-in or
Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-in: No property data stored
centrally.
|
|
|
|
Repository: Select the repository
file where the properties are stored. The fields that follow after
are completed automatically using the data retrieved.
|
|
|
Use an existing connection
|
Select this check box and in the Component List click the
relevant connection component to reuse the connection details you already defined.
Note
When a Job contains the parent Job and the child Job, if you need to share an existing
connection between the two levels, for example, to share the connection created by the
parent Job with the child Job, you have to:
-
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
Talend Studio User
Guide.
|
|
|
Host
|
Database server IP address.
|
|
|
Port
|
Listening port number of the DB server.
|
|
|
Database
|
Name of the database.
|
|
|
Username and
Password
|
DB user authentication data.
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.
|
|
|
Schema and Edit
Schema
|
A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-In: You create and store the schema locally for this
component only. Related topic: see Talend Studio
User Guide.
|
|
|
|
Repository: You have already created the schema and
stored it in the Repository. You can reuse it in various projects and Job designs. Related
topic: see Talend Studio User Guide.
|
| |
|
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.
|
|
|
Table Name
|
Name of the table to be processed.
|
|
|
Query type
|
Either Built-in or
Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-in: Fill in the query
statement manually or build it graphically using the
SQLBuilder.
|
|
|
|
Repository: Select the relevant
query stored in the Repository. The Query field is filled in accordingly.
|
|
|
Guess Query
|
Click this button to generate a query that corresponds to your
table schema in the Query
field.
|
|
|
Query
|
Enter your DB query taking care to sequence the fields properly 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
|
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.
Note
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.
|
|
|
Use PreparedStatement
|
Select this check box if you want to query the database using a
PreparedStatement. In the Set
PreparedStatement Parameter table, define the
parameters represented by “?” in the SQL instruction of the
Query field in the Basic Settings tab.
Parameter Index: Enter the
parameter position in the SQL instruction.
Parameter Type: Enter the parameter
type.
Parameter Value: Enter the
parameter value.
Note
This option is very useful if you need to execute the same
query several times. Performance levels are increased
|
|
|
Commit every
|
Number of rows to be completed before committing batches of rows
together into the DB. This option ensures transaction quality (but
not rollback) and above all better performance on executions.
|
|
|
tStat
Catcher Statistics
|
Select this check box to collect log data at the component
level.
|
|
Global Variables
|
QUERY: the SQL 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 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 further information about variables, see Talend Studio
User Guide.
|
|
Usage
|
This component offers the flexibility of the DB query and covers
all possible SQL queries.
|
|
Log4j
|
The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User
Guide.
For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.
|
|
Limitation
|
Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on
the Modules tab in the Integration perspective
of your studio. For details, see https://help.talend.com/display/KB/How+to+install+external+modules+in+the+Talend+products
or the section describing how to configure the Studio in the Talend Installation and Upgrade
Guide.
|
