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

tPaloInputMulti Properties

Component family

Business Intelligence/Cube OLAP/Palo

 

Function

This component retrieves data (elements as well as values) from a Palo cube.

Purpose

This component retrieves the stored or calculated values in combination with the element records out of a 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 elements of interest reside.

 

Cube

Type in the name of the cube where the dimension elements to be retrieved are stored.

 

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

 

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.

 

Cube Query

Complete this table with the query you want to use to retrieve data. The columns to be filled are:

 

 

Column: the schema columns are added automatically to this column once defined in the schema editor. The schema columns are used to stored the retrieved dimension elements.

 

 

Dimensions: type in each of the dimension names of the cube from which you want to retrieve dimension elements.

Warning

The dimension order listed in this column must be consistent with the order given in the cube that stores these dimensions.

 

 

Elements: type in the dimension elements from which data is retrieved. If several elements are needed from one single dimension, separate them with a coma.

Advanced settings

tStat Catcher Statistics

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

Connections

Outgoing links (from this component to another):

Row: Main

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

Incoming links (from one component to this one):

Row: Iterate

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

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

According to the architecture of OLAP-Systems only one single value (text or numeric) could be retrieved from the cube. The MEASURE column and the TEXT column are fixed and read-only.

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: Retrieving dimension elements from a given cube

The Job in this scenario retrieves several dimension elements from a demo Palo cube Sales.

To replicate this scenario, proceed as follows:

Setting up the Job

  1. Drop tPaloInputMulti and tLogRow from the component Palette onto the design workspace.

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

  3. In the menu, select Row > Main to connect tPaloInputMulti to tLogRow with a row link.

Setting up the DB connection

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

  2. In the Host name field, type in the host name or the IP address of the host server, localhost for this example.

  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.

Configuring the Cube Query

  1. In the Database field, type in the database name in which the cube to be used is stored.

  2. In the Cube field, type in the cube name in which the dimensions of interests are stored. In this scenario, it is one of the demo cubes Sales.

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

  4. Next to the Edit schema field, click the three-dot button to open the schema editor.

  5. In the schema editor, click the plus button to add the rows of the schema to be edited. In this example, add rows corresponding to all of the dimensions stored in the Sales cube: Products, Regions, Months, Years, Datatypes, Measures. Type in them in the order given in this cube.

  6. Click OK to validate this editing and accept the propagation of this change to the next component. Then these columns are added automatically into the Column column of the Cube query table in the Component view. If the order is not consistent with the one in the Sales cube, adapt it using the up and down arrows under the schema table.

  7. In the Dimensions column of the Cube query table, type in each of the dimension names stored in the Sales cube regarding to each row in the Column column. In the Sales cube, the dimension names are: Products, Regions, Months, Years, Datatypes, Measures.

  8. In the Elements columns of the Cube query table, type in the dimension elements you want to retrieve regarding to the dimensions they belong to. In this example, the elements to be retrieved are All Products, Germany and Austria (Belonging to the same dimension Regions, these two elements are entered in the same row and separated with a coma.), Jan, 2009, Actual, Turnover.

Job execution

  1. Click tLogRow to open its Component view.

  2. In the Mode area, select the Table (print values in cells of a table) check box to display the execution result in a table.

  3. Press F6 to run the Job.

The dimension elements and the corresponding Measure values display in the Run console.