Mapping File

Mon, 01 Jan 0001 00:00:00 +0000

Overview

At minimum, one mapping.json file must be uploaded to the S3 bucket in the root folder. If multiple folders exist in the S3 bucket then each folder can have it’s own mapping.json. When nested folders exist in the bucket, S3 protector will look for a mapping file starting with the same folder as the data file and moving up the directory tree until root folder is reached.

Configuration Structure

The mapping.json file must be formatted in valid JSON with the key-values configuration pairs described below:

Column Mapping Rules

Mon, 01 Jan 0001 00:00:00 +0000

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