Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Microsoft Azure Data Lake Storage Gen2 source properties

Microsoft Azure Data Lake Storage Gen2 source properties

In a
file ingestion
task, you can configure the Microsoft Azure Data Lake Storage Gen2 source properties to transfer files from a Microsoft Azure Data Lake Storage Gen2 source to a Microsoft Azure Data Lake Storage Gen2 target or any target that a
file ingestion
task supports. The source options vary based on the file pickup method that you select for the task.
When the task transfers files from a Microsoft Azure Data Lake Storage Gen2 source to a Databricks Delta target, the files must be of Parquet format and must have the same schema as the Databricks Delta target.
You can overwrite the file name pattern, folder, and table parameters, and define your own variable for sources by using the job resource of the Mass Ingestion Files REST API. For more information, see Mass Ingestion Files REST API.
The following table describes the source options:
Advance Source Property
Description
File Pickup
The file ingestion task supports the following file pickup methods:
  • By Pattern
    . The file ingestion task picks up files by pattern.
  • By File List
    . The file ingestion task picks up files based on a file list.
Source Directory
Microsoft Azure Data Lake Storage Gen2 folder path from where files are transferred. The default value is the container path specified in the connection.
You can enter a relative path to the source file system. To enter a relative path, start the path with a period, followed by a slash (./). The path is relative to the source directory specified in the connection.
Add Parameters
Create an expression to add it as a
Source Directory
parameter. For more information, see Add Parameters.
Include files from sub-folders
This applies when
File Pickup
is
By Pattern
. Transfer files from sub-folders present in the folder path.
File Pattern
This applies when
File Pickup
is
By Pattern
. File name pattern used to select the files to transfer. You can use a regular expression or wildcard characters.
The following wildcard characters are allowed:
  • An asterisk (*) to represent any number of characters.
  • A question mark (?) to represent a single character.
For example, you can specify the following regular expression:
([a-zA-Z0-9\s_\\.\-\(\):])+(.doc|.docx|.pdf)$
File Date
This applies when
File Pickup
is
By Pattern
. A date and time expression for filtering the files to transfer.
Select one of the following options:
  • Greater than or Equal
    . Filters files that are modified on or after the specified date and time.
    To specify a date, click the calendar. To specify a time, click the clock.
  • Less than or Equal
    . Filters files that are modified before or on the specified date and time.
  • Equal
    . Filters files that are modified on the specified date and time.
    Click the calendar to select the date and the clock to select the time.
  • Days before today
    . Filters files that are modified within the specified number of days until the current date (today). Enter the number of days. The current date calculation starts from 00:00 hours.
For example, if you schedule the
file ingestion
task to run weekly and want to filter for the files that were modified in the previous week, set
Days before today
to 7. The task will pick up any file with a date between 7 days ago and the date on which it runs.
Time Zone
This applies when
File Pickup
is
By Pattern
. If you selected a
File Date
option, enter the time zone of the location where the files are located.
File Size
This applies when
File Pickup
is
By Pattern
. Filters the files to transfer based on file size. Enter the file size, select the file size unit, and filter options.
Select one of the following filter options:
  • Greater than or Equal
    . Filters files that are greater than or equal to the specified size.
  • Less than or Equal
    . Filters files that are less than or equal to the specified size.
  • Equal
    . Filters files that have the specified size.
The file path containing the list of files
This applies when
File Pickup
is
By File List
. Select this option to provide the path that contains the list of files to pick up and enter the file path.
File list
This applies when
File Pickup
is
By File List
. Select this option to provide the list of files to pick up and enter a comma-separated list of file names.
Skip duplicate files
Do not transfer duplicate files. If files with the same name and creation date were transferred by the same
file ingestion
task, the task does not transfer them again, and the files are marked as duplicate in the job log. If this option is not selected the task transfers all files.
Check file stability
Indicates whether to verify that a file is stable before a file ingestion task attempts to pick it. The task skips unstable files it detects in the current run.
Stability check interval
This applies when you enable the
Check file stability
option. Time in seconds that a file ingestion task waits to check the file stability.
For example, if the stability time is 15 seconds, the file ingestion task detects all the files in the source folder that match the defined file pattern, it waits for 15 seconds, and then it processes only the stable files.
The interval ranges between 10 seconds to 300 seconds. Default is 10 seconds.
Batch Size
The number of files a
file ingestion
task can transfer in a batch.
Default is 5.
The maximum batch size varies, based on the following conditions:
  • If the task transfers files from source to target with no intermediate staging, the maximum number of files the task can transfer in a batch is 8000.
  • If the task transfers files from source to target with intermediate staging, the maximum number of files the task can transfer in a batch is 20.
  • If the task transfers files from any source to a Snowflake or Databricks Delta target, the maximum number of files the task can transfer in a batch is 1000.
If you transfer files from Microsoft Azure Data Lake Storage Gen2 to Azure SQL Data Warehouse, the task transfers files with no intermediate staging.
Block Size (Bytes)
Divides a large file into smaller specified block size. When you read a large file, divide the file into smaller parts and configure concurrent connections to spawn the required number of threads to process data in parallel.
Default is 8388608 bytes (8 MB).
After File Pickup
Determines what to do with source files after the files transfer. The following options are available:
  • Keep files in the source directory.
  • Delete files from the source directory.
  • Rename files in the source directory. You must specify a file name suffix that File Ingestion adds to the file name when renaming the files.
  • Archive the files to a different location. You must specify an archive directory which is the absolute path or relative path from the source file system.

0 COMMENTS

We’d like to hear from you!