Dedup removes duplicate records.
|Input||0||✓||for input data records||any|
|Output||0||✓||For deduplicated data records.||equal input metadata|
|1||⨯||For duplicate data records.|
Metadata can be propagated through this component.
Dedup has no metadata template.
Dedup does not require any specific metadata fields.
|Dedup key|| |
A key according to which the records are deduplicated.
If the Dedup key is not set, the whole input is considered as one group. Therefore the Number of duplicates attribute specifies the number of records that are send to the output.
If the Dedup key is set, only a specified number of records with the same values in fields specified as the Dedup key is picked up. See Dedup key.
Defines which records will be preserved.
|First (default) | Last | Unique|
|Sorted input||Assume input as sorted. See Sorted versus Unsorted Input.||true (default) | false|
By default, records with null values of key fields are considered to be equal.
|true (default) | false|
|Number of duplicates|
The maximum number of duplicate records to be selected from each group of adjacent records
with an equal key value or, if the key is not set, maximum number of records
from the beginning or the end of all records.
Ignored if the
|1 (default) | 1-N|
Dedup reads data flow of records grouped by the same values of the Dedup key.
The key is formed by field name(s) from input records.
If no key is specified, the component behaves like the Unix
The groups don't have to be ordered.
The component can select a specified number of the first or the last records from the group or from the whole input. Only those records with no duplicates can be selected, too.
The deduplicated records are sent to output port 0. The duplicate records may be sent through output port 1.
The component can process sorted input data as well as partially sorted ones. When setting the fields composing the Dedup key, choose the proper Order attribute:
Ascending - if the groups of input records with the same key field value(s) are sorted in ascending order
Descending - if the groups of input records with the same key field value(s) are sorted in descending order
Auto - the sorting order of the groups of input records is guessed from the first two records with different value in the key field, i.e. from the first records of the first two groups.
Ignore - if the groups of input records with the same key field value(s) are not sorted
Sorted versus Unsorted Input
Dedup can process data in two modes: sorted and unsorted.
If you want to process a huge number of records with many different key values, sort the records first and then use Dedup with Sorted input.
If your data contains a few different key values, you can use unsorted input. Dedup with unsorted input does not require pre-sorting, but is confined with main memory available as the records to be sent to the first output port are cached in memory.
The requirements on main memory in unsorted mode depend on values of the Number of duplicates and Keep attributes. Lower number of duplicates means less memory is necessary. Selecting several first records requires less memory than several last.
Unsorted Input Records and Order of Output Records
If you use unsorted input records, the order of output records is not guaranteed to be the same as the the order of input records.
If you keep First record(s), the order on both output ports is preserved.
If you keep Last record(s), the order within any group with the same key is preserved on both output ports. The order of records on the second output port is not guaranteed.
If you keep Unique records, the order of unique records on the first output port is preserved. The order of records on the second output port may be arbitrary.
|Dedup Sorted Records|
|Dedup Unsorted Records|
|Sending out the first N records|
Dedup Sorted Records
This example shows the usage of Dedup with sorted input records. This case is suitable for a big number of records with many different key values.
An access log contains IPaddress and timestamp. Records are sorted in ascending order according to the IPaddress and timestamp. For each IPaddress, find timestamp of the first access. Null values do not appear in the data.
Set the Dedup key and Keep attributes.
By default, the number of duplicates is one, therefore it does not have to be set up.
Dedup Unsorted Records
This example shows the usage of Dedup with unsorted input records. This case is suitable for datasets with a small number of different key values.
An access log contains timestamp, username, and IPaddress fields. The records are sorted in ascending order according to the timestamp. The log contains a huge number of records but there are not so many different usernames. Your task is to filter out last two logins for each user.
Set Sorted input and Number of duplicates.
|Number of duplicates||2|
Sorted input is set to
as records are not sorted according to Dedup key.
Timestamp is not Dedup key.
Note that the order of records sent to the output port may be different from the order of records received from the input port.
Sending out the first N records
The previous component (A) sends out a variable number of records. Send the first 100 records to the component B and send the other records to the component C.
Connect the input port of Dedup with component A; the first output port with component B; and the second output port with component C.
Set the Number of duplicates attribute.
|Number of duplicates||100|
You can use Dedup to partition records in this way, if Dedup key is not set.
|4.3.0-M1||You can now use Dedup with unsorted input records.|