tPaloOutputMulti - 6.1

Talend Components Reference Guide

EnrichVersion
6.1
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

tPaloOutputMulti Properties

Component family

Business Intelligence/Cube OLAP/Palo

 

Function

This component writes data (elements as well as values) into a Palo cube.

Purpose

This component takes the input stream and writes it to a given Palo cube.

Basic settings

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, Component List presents only the connection components in the same Job level.

Connection configuration

Note

Unavailable when using an existing connection.

Host Name

Enter the host name or the IP address of the host server.

 

Server Port

Type in the listening port number of the Palo server.

 

Username and Password

Enter the Palo 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.

 

Database

Type in the name of the database where the cube of interest resides.

 

Cube

Type in the name of the cube in which the incoming data is written.

 

Cube type

Select the cube type from the drop-down list for the cube of concern. This type may be:

- Normal

- Attribut

- System

- User Info

 

Commit size

Type in the row count of each batch to be written into the cube.

 

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. 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.

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. Related topic: see Talend Studio User Guide.

 

 

Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: see Talend Studio User Guide.

 

Measure value

Select the column from the input stream which holds the Measure or Text values.

 

Splash mode

Select the splash mode used to write data into a consolidated element. The mode may be:

- Add: it writes values to the underlying elements.

- Default: it uses the default splash mode.

- Set: it simply sets or replaces the current value and make the distribution based on the other values.

- Disable: it applies no splashing.

For further information about the Palo splash modes, see Palo's user guide.

 

Add values

Select this check box to add new values to the current values for a sum. Otherwise these new values will overwrite the current ones.

 

Use eventprocessor

Select this check box to call the supervision server.

 

Die on error

This check box is cleared by default, meaning to skip the row on error and to complete the process for error-free rows.

Advanced settings

tStat Catcher Statistics

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

 

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:

  • Enter the number of parallel executions desired.

  • Press Ctrl + Space and select the appropriate context variable from the list. For further information, see Talend Studio User Guide.

Warning

  • The Action on table field is not available with the parallelization function. Therefore, you must use a tCreateTable component if you want to create a table.

  • When parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subjob.

Connections

Outgoing links (from this component to another):

Row: Main

Trigger: Run if; On Component Ok; On Component Error.

Incoming links (from one component to this one):

Row: Main; Reject

For further information regarding connections, see Talend Studio User Guide.

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 further information about variables, see Talend Studio User Guide.

Usage

This component requires an input component.

Log4j

If you are using a subscription-based version of the Studio, 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

Numeric measures are only be accepted as Double or String type. When the string type is used, write the value to be processed between quotation marks.

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 Guide.

Scenario 1: Writing data into a given cube

The Job in this scenario writes new values in the Sales cube given as demo in the Demo database installed with Palo.

To replicate this scenario, proceed as follows:

Setting up the Job

  1. Drop tFixedFlowInput and tPaloOutputMulti from the component Palette onto the design workspace.

  2. Right-click tFixedFlowInput to open its contextual menu.

  3. In this menu, select Row > Main to connect this component to tPaloOutputMulti.

Configuring the input component

  1. Double-click the tFixedFlowInput component to open its Component view.

  2. Click the three-dot button to open the schema editor.

  3. In the schema editor, click the plus button to add 7 rows and rename them respectively as Products, Regions, Months, Years, Datatypes, Measures and Values. The order of these rows must be consistent with that of the corresponding dimensions in the Sales cube and the type of the Value column where the measure value resides is set to double/Double.

  4. Click OK to validate the editing and accept the propagation prompted by the dialog box that pops up. Then the schema column labels display automatically in the Value table under the Use single table check box, in the Mode area.

  5. In the Value table, type in values for each row in the Value column. In this example, these values are: Desktop L, Germany, Jan, 2009, Actual, Turnover, 1234.56.

Configuring the output component

  1. Double-click tPaloOutputMulti to open its Component view.

  2. In the Server Port field, type in the listening port number of the Palo server. In this scenario, it is 7777.

  3. In the Username field and the Password field, type in the authentication information. In this example, both of them are admin.

  4. In the Database field, type in the database name in which you want to create the cube, Demo in this example.

  5. In the Cube field, type in the name of the cube you want to write data in, for example, Sales.

  6. In the Cube type field, select the Normal type from the drop-down list for the cube to be created, meaning this cube will be normal and default.

  7. In the Measure Value field, select the Measure element. In this scenario, select Value.

Job execution

Press F6 to run the Job.

The inflow data has been written into the Sales cube.

Scenario 2: Rejecting inflow data when the elements to be written do not exist in a given cube

The Job in this scenario tries to write data into the Sales cube but as the elements of interest do not exist in this cube, the inflow data is rejected.

To replicate this scenario, proceed as follows:

Setting up the Job

  1. Drop tFixedFlowInput, tPaloCheckElements, tPaloOutputMulti and tLogRow from the component Palette onto the design workspace.

  2. Right-click tFixedFlowInput to open its contextual menu.

  3. In this menu, select Row > Main to connect this component to tPaloCheckElements.

  4. Do the same to connect tPaloOutputMulti using row link.

  5. Right-click tPaloCheckElements to open its contextual menu.

  6. In this menu, select Row > Reject to connect this component to tLogRow.

Configuring the input component

  1. Double-click the tFixedFlowInput component to open its Component view.

  2. Click the three-dot button to open the schema editor.

  3. In the schema editor, click the plus button to add 7 rows and rename them respectively as Products, Regions, Months, Years, Datatypes, Measures and Values. The order of these rows must be consistent with that of the corresponding dimensions in the Sales cube and the type of the Value column where the measure value resides is set to double/Double.

  4. Click OK to validate the editing and accept the propagation prompted by the dialog box that pops up. Then the schema column labels display automatically in the Value table under the Use single table check box, in the Mode area.

  5. In the Value table, type in values for each row in the Value column. In this example, these values are: Smart Products, Germany, Jan, 2009, Actual, Turnover, 1234.56. The Smart Products element does not exist in the Sales cube.

Configuring the tPaloCheckElements component

  1. Double-click tPaloCheckElements to open its Component view.

  2. In the Host name field, type in localhost.

  3. In the Server Port field, type in the listening port number of the Palo server. In this scenario, it is 7777.

  4. In the Username field and the Password field, type in the authentication information. In this example, both of them are admin.

  5. In the Database field, type in the database name in which you want to create the cube, Demo in this example.

  6. In the Cube field, type in the name of the cube you want to write data in, for example, Sales.

  7. In the On Element error field, select Reject row from the drop-down list.

  8. In the element table at the bottom of the Basic settings view, click the Element type column in the Value row and select Measure from the drop down list.

Configuring the output component

  1. Double-click tPaloOutputMulti to open its Component view.

  2. In the Server Port field, type in the listening port number of the Palo server. In this scenario, it is 7777.

  3. In the Username field and the Password field, type in the authentication information. In this example, both of them are admin.

  4. In the Database field, type in the database name in which you want to create the cube, Demo in this example.

  5. In the Cube field, type in the name of the cube you want to write data in, for example, Sales.

  6. In the Cube type field, select the Normal type from the drop-down list for the cube to be created, meaning this cube will be normal and default.

  7. In the Measure Value field, select the Measure element. In this scenario, select Value.

Job execution

Press F6 to run the Job.

The data to be written is rejected and displayed in the console of the Run view. You can read that the error message is Smart Products.