Microsoft Azure Data Lake Storage Gen2 Connector

Back Next

Writing to target objects

When you import target objects, the Secure Agent appends a FileName field to the imported target object. When you map the FileName field in the target object to an incoming field, the Secure Agent creates the folder structure and the target files based on the FileName field.

The following table describes how the Secure Agent reads file names for mappings:

Format type	Syntax	Example
Complex file	<directory>/<target_file_name>/<target_file_name>=<values of filename field>/part_file	parquet/writer/customer.parquet/customer.parquet=1
Flat file	<directory>/<target_file_name>/<target_file_name>=<values of filename field>/part_file This syntax is applicable only to mappings. If you create a mapping in advanced mode, the Secure Agent does not create a directory structure.	csv/customer.csv/customer.csv=1

The following table describes the syntax and example for the FileName field scenarios in mappings:

Description	Syntax	Example
When there is no target, a new target file is created.	<target_file_name>=<source_file_name>	customer_tgt.csv=customer_src.csv
When the FileName field of an source is mapped to the FileName field of an existing target, a new target file is created and the existing target is not affected.	<target_file_name>=<source_field_value>	customer_tgt.csv=customer_src.csv
When a source field other than the FileName field is mapped to the FileName field of an existing target, separate files are created for each unique value of the source field.	<target_file_name>=<source_field_value>	customer_tgt.csv=a, customer_tgt.csv=b... customer_tgt.csv=n In the example, n number of files are inserted into the directory where the target file is present. Where, n equals the number of unique values of the source field.

Rename Saved Search

Table of Contents

Microsoft Azure Data Lake Storage Gen2 Connector

Microsoft Azure Data Lake Storage Gen2 Connector

Writing to target objects

Writing to target objects