Column Mapping Rules
In order to ensure highest level of security, the S3 Protector requires users to define processing rules for all data columns. Every column that appears in a source file must be mentioned in the ‘mapping.json’ file. A column may appear in either ‘columns’ section or ‘ignored-columns’ section, but not both.
Common Error Conditions
The table below summaries common error conditions that may occur when creating a ‘mapping.json’ file:
| Mapping | Error Message |
|---|---|
| A column name appears in ‘mapping.json’ but does not exist in the source file. | Columns [‘column name’] in the mapping file have no matches in the input data columns |
| Source file column name appears neither in ‘columns’ nor ‘ignored-columns’ sections. | Input file contains data columns which are not defined in the mapping file. |
| Source file column name appears in both ‘columns’ and ‘ignored-columns’ sections. | Ignored column [‘column-name’] is present in ‘columns’ list. Column must be defined in either ‘columns’ or ‘ignored-columns’, but not both. |
| Source file column name appears more than once in either ‘columns’ or ‘ignored-columns’ section. | Duplicate column [“column-name”] found in ‘ignored-columns’. |
Note
The column names in the mapping file are case sensitive.Feedback
Was this page helpful?