tPaloRuleList - 6.1

Talend Components Reference Guide

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
Talend Studio
Data Governance
Data Quality and Preparation
Design and Development

tPaloRuleList Properties

Component family

Business Intelligence/Cube OLAP/Palo



This component retrieves a list of rule details from the given Palo database.


This component lists all rules, formulas, comments, activation status, external IDs from a given 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.


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


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.



The name of the database where the cube of interest resides.



Type in the name of the cube in which you want to retrieve the rule information.


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.

Advanced settings

tStat Catcher Statistics

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

Global Variables

NB_RULES: the number of rules. This is an After variable and it returns an integer.

EXTERNAL_RULEID: the external ID of the rule. 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.


Outgoing links (from this component to another):

Row: Main; Iterate.

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.


This component can be used in standalone or as start component of a process.


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


The output schema is 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 or the section describing how to configure the Studio in the Talend Installation Guide.

Discovering the read-only output schema of tPaloRuleList

The following table presents information related to the read-only output schema of the tPaloRuleList component.






The internal identifier/id for this rule..



The formula of this rule. For further information about this formula, see the Palo user guide.



The user-defined external id.



The user-edited comment on this rule.



Indicates if this rule had been activated or not.

Scenario: Retrieving detailed rule information from a given cube

The Job in this scenario retrieves rule details applied on the dimensions of a given cube.

To replicate this scenario, proceed as follows:

Setting up the Job

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

  2. Right-click tPaloRuleList to open the contextual menu.

  3. From this menu, select Row > Main to link the two components.

Configuring the tPaloRuleList component

  1. Double-click the tPaloRuleList 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 and Password fields, type in the authentication information. In this example, both of them are admin.

  5. In the Database field, type in the database name where the dimensions applying the rules of interest reside, Biker in this example.

  6. In the Cube field, type in the name of the cube which the rules of interest belong to.

Job execution

Press F6 to run the Job.

Details of all of the rules in the Orders cube are retrieved and listed in the console of the Run view.

For further information about the output schema, see Discovering the read-only output schema of tPaloRuleList.