The query language used with data stewardship components and the REST API
You can use Talend Query Language (TQL) with the tDataStewardshipTaskDelete and tDataStewardshipTaskInput components to query and filter the data you want to delete or read from Talend Data Stewardship.
Syntax in TQL queries
The query statement used to filter tasks on the server is composed of one or several conditions.
A task condition is composed of the following elements:
- a field name, which must be prefixed by
record.when referencing records data, - an operator, and
- a value, which can be any literal value. Use simple quotes around strings, and precede quotes within the string with a backslash.
The fields you can query with TQL
Field names can be chosen among all custom and metadata fields.
The following table lists the supported metadata fields on tasks:
| Metadata field | Description |
|---|---|
| id (string) | Task internal identifier |
| externalID (string) | Task external identifier which helps to access a given task from an external system |
| currentState (string) | Current state of the task in the campaign workflow |
| assignee (string) | userId of the data steward currently assigned to this task |
| targetTransition (string) | Name of the transition chosen by user to move the task to the next step in the campaign workflow |
| completed (boolean) | true if the task is completed (it is in a final state of the workflow) |
| priority (integer) | Priority level of the task, ranging from 0 (Very Low) to 4 (Very High), default is 2 (Medium) |
| dueDate | Timestamp in milliseconds of the task due date |
| matchScore (only for Merging and Grouping campaigns) | Decimal value which shows the highest match score of each group in the source data |
| version (integer) | Integer value of the task version which is incremented whenever the task is updated |
| consumed (boolean) | true if the task has already been processed (so it cannot be processed anymore - unless it is reopened) |
| createdBy (string) | userId of the task creator |
| creationDate (long) | Timestamp in milliseconds of this task creation date |
| lastUpdatedBy (string) | userId of the data steward who did the last update on the task |
| lastUpdateDate (long) | Timestamp in milliseconds of the last update done on the task |
| tags (string) | List of tags entered by the user for this task |
| arbitration (only for Arbitration and Grouping campaigns) | Arbitration choice selected by the data steward |
Binary operators supported in TQL
| Operator (TQL symbol) | Description |
|---|---|
= |
Returns a result which matches the value entered. |
!= |
Returns a result of any value other than the value entered. |
> |
Returns a result which is greater than the value entered. |
>= |
Returns a result which is greater than or equal to the value entered. |
< |
Returns a result which is less than the value entered. |
<= |
Returns a result which is less than or equal to the value entered. |
creationDate > 1451659712733Boolean operators supported in TQL
You can combine or negate conditions using the boolean operators
and and or, or
the not operator respectively. Parentheses are
supported to override default boolean precedence.
For example, you can filter tasks by assignee and have a record field firstname equal to John using the following query:
assignee='user1@talend.com' and record.firstName='John'You can also filter tasks by assignee and have a record field
firstname equal to De'wayne using the following
query:
assignee='user2@talend.com' and record.firstName='De\'wayne'