Azure Data Lake Storage as Target
Fivetran HVR supports integrating changes into Azure Data Lake Storage (DLS) location. This section describes the configuration requirements for integrating changes using Integrate and Refresh into ADLS location.
Due to technical limitations, Azure Data Lake Storage is not supported in the HVR releases since 6.1.5/3 to 6.1.5/9.
Customize Integrate
Defining action Integrate is sufficient for integrating changes into an ADLS location. However, the default file format written into a target file location is HVR'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 actions 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 | * | FileFormat | This action may be defined to:
|
ADLS | * | Integrate | To segregate and name the files integrated into the target location, define parameter RenameExpression. 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 | * | ColumnProperties | This action defines properties for a column being replicated. This action may be defined to:
|
Integrate Limitations
By default, for file-based target locations, HVR does not replicate the delete
operation performed at the source location.