Azure Data Lake Storage as Target

Fivetran Local Data Processing supports integrating changes into Azure Data Lake Storage (DLS) location. This section describes the configuration requirements for integrating changes using and into ADLS location.

Customize Integrate

Defining action is sufficient for integrating changes into an ADLS location. However, the default written into a target file location is Local Data Processing's own XML format and the changes captured from multiple tables are integrated as files into one directory. The integrated files are named using the integrate timestamp.

You may define other for customizing the default behavior of integration mentioned above. Following are few examples that can be used for customizing integration into the ADLS location:

Group	Table	Action	Annotation
ADLS	*		This action may be defined to: specify the format (, , , , or ) of the files integrated into the target location. escape any delimiters (e.g. comma) present in a column using the parameter . escape the quote character () defined, using the parameter .
ADLS	*		To segregate and name the files integrated into the target location, define parameter . For example, if RenameExpression={hvr_tbl_name}/{hvr_integ_tstamp}.csv is defined, then for each table in the source, a separate folder (with the same name as the table name) is created in the target location, and the files replicated for each table are saved into these folders. This also enforces unique name for the files by naming them with a timestamp of the moment when the file was integrated into the target location.
ADLS	*		This action defines properties for a column being replicated. This action may be defined to: integrate the delete operation. By default, for file-based target locations, Local Data Processing does not replicate the delete operation performed at the source location. So to integrate the delete operation, an extra column for timekey needs to be added in the target location. For this, action may be defined with the following parameters: : This parameter defines the name for the extra column in the target location. : This parameter defines that this is an extra column in the target location (a column which is not present in the source location). : This parameter defines the expression to be used for generating the timekey value. For example, {hvr_integ_seq} can be used here. This is a 36 byte string value (hex characters) which is unique and continuously increasing for a specific source location. : This parameter defines that this is a timekey column. =varchar: This parameter defines the data type for the extra column. =36: This parameter defines the data type length for the extra column. add the source operation type (using ) information in the target location. This action definition is required for performing if action with parameter is defined on a target file location. For this, action may be defined with the following parameters: : This parameter defines the name for the extra column in the target location. : This parameter defines that this is an extra column in the target location (a column which is not present in the source location). ={hvr_op}: This parameter defines the expression to be used for generating the information about source operation type. =integer: This parameter defines the data type for this extra column.

Integrate Limitations

By default, for file-based target locations, Local Data Processing does not replicate the delete operation performed at the source location.