The Post Map Values element in the filter field names as keys, the values are lists of sets of post map values, each describing one mapping done on a field named before obtained after filtering.
Currently there are four kind of mappings are supported:
The name of the mapping element should be map_date. The value json element may contain the following parameters:
| Field | Description |
|---|---|
| src_date_pattern | If it is specified than the mapper converts from this format to the target, and also adds missing year |
| target_date_pattern | If ‘epoch’ then the field is parsed as seconds from 1970, otherwise the content used as pattern |
The name of the mapping element should be map_copy. The value json element should contain the following parameter:
| Field | Description |
|---|---|
| copy_name | The name of the copied field |
The name of the mapping element should be map_fieldname. The value json element should contain the following parameter:
| Field | Description |
|---|---|
| new_field_name | The name of the renamed field |
The name of the mapping element should be map_fieldvalue. The value json element should contain the following parameter:
| Field | Description |
|---|---|
| pre_value | The value that the field must match (ignoring case) to be mapped |
| post_value | The value to which the field is modified to |
The name of the mapping element should be map_anonymize. The value json element should contain the following parameter:
| Field | Description |
|---|---|
| pattern | The pattern to use to identify parts to anonymize. The parts to hide should be marked with the “” string. |
| hide_char | The character to hide with, if it is not specified then the default is ‘*’ |