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

Flat File target properties

Flat File target properties

When you define a
database ingestion
task, you must enter some properties for your Flat File target on the
Target
page of the task wizard.
For flat file targets, these properties apply to initial load jobs only.
Under
Target
, you can enter the following Flat File target properties:
Property
Description
Output Format
Select the format of the output file. Options are:
  • CSV
  • AVRO
The default value is
CSV
.
Output files in CSV format use double-quotation marks ("") as the delimiter for each field.
Add Headers to CSV File
If
CSV
is selected as the output format, select this check box to add a header with source column names to the output CSV file.
Avro Format
If you selected
AVRO
as the output format, select the format of the Avro schema that will be created for each source table. Options are:
  • Avro-Flat
    . This Avro schema format lists all Avro fields in one record.
  • Avro-Generic
    . This Avro schema format lists all columns from a source table in a single array of Avro fields.
  • Avro-Nested
    . This Avro schema format organizes each type of information in a separate record.
The default value is
Avro-Flat
.
Avro Serialization Format
If
AVRO
is selected as the output format, select the serialization format of the Avro output file. Options are:
  • None
  • Binary
  • JSON
The default value is
Binary
.
Avro Schema Directory
If
AVRO
is selected as the output format, specify the local directory where
Mass Ingestion Databases
stores Avro schema definitions for each source table. Schema definition files have the following naming pattern:
schemaname
_
tablename
.txt
If this directory is not specified, no Avro schema definition file is produced.
File Compression Type
Select a file compression type for output files in CSV or AVRO output format. Options are:
  • None
  • Deflate
  • Gzip
  • Snappy
The default value is
None
, which means no compression is used.
Avro Compression Type
If
AVRO
is selected as the output format, select an Avro compression type. Options are:
  • None
  • Bzip2
  • Deflate
  • Snappy
The default value is
None
, which means no compression is used.
Deflate Compression Level
If
Deflate
is selected in the
Avro Compression Type
field, specify a compression level from 0 to 9. The default value is 0.
Data Directory
For initial load tasks, define a directory structure for the directories where Mass Ingestion Databases stores output data files and optionally stores the schema. To define directory pattern, you can use the following types of entries:
  • The placeholders {SchemaName}, {TableName), {Timestamp}, {YY}, {YYYY}, {MM}, and {DD}, where {YY}, {YYYY}, {MM}, and {DD} are for date elements. The {Timestamp} values are in the format yyyymmdd_hhmissms. The generated dates and times in the directory paths indicate when the initial load job starts to transfer data to the target.
  • Specific directory names.
  • The toUpper() and toLower() functions, which force the values for an associated (
    placeholder
    ) to uppercase or lowercase.
Placeholder values are not case sensitive.
Examples:
myDir1/{SchemaName}/{TableName} myDir1/myDir2/{SchemaName}/{YYYY}/{MM}/{TableName}_{Timestamp} myDir1/{toLower(SchemaName)}/{TableName}_{Timestamp}
The default directory pattern is
{TableName)_{Timestamp}
.
For Amazon S3, Flat File, and Microsoft Azure Data Lake Storage Gen2 targets, Mass Ingestion Databases uses the directory specified in the target connection properties as the root for the data directory path when
Connection Directory as Parent
is selected. For Google Cloud Storage targets, Mass Ingestion Databases uses the
Bucket
name that you specify in the target properties for the ingestion task.
Connection Directory as Parent
For initial load tasks, select this check box to use the directory value that is specified in the target connection properties as the parent directory for the custom directory paths specified in the task target properties. The parent directory is used in the
Data Directory
and
Schema Directory
.
Schema Directory
For initial load tasks, you can specify a custom directory in which to store the schema file if you want to store it in a directory other than the default directory. This field is optional.
The schema is stored in the data directory by default. For incremental loads, the default directory for the schema file is
{TaskTargetDirectory}/data/{TableName}/schema
.
You can use the same placeholders as for the
Data Directory
field. Ensure the placeholders are enclosed in curly brackets { }.
Under
Advanced
, the following table describes the Flat File target advanced properties that appear:
Field
Description
Add Operation Type
Select this check box to add a metadata column that includes the source SQL operation type in the output that the job propagates to the target.
For incremental loads, the job writes "I" for insert, "U" for update, or "D" for delete. For initial loads, the job always writes "I" for insert.
By default, this check box is cleared.
Add Operation Time
Select this check box to add a metadata column that includes the source SQL operation time in the output that the job propagates to the target.
For initial loads, the job always writes the current date and time.
By default, this check box is cleared.
Add Operation Owner
Select this check box to add a metadata column that includes the owner of the source SQL operation in the output that the job propagates to the target.
For initial loads, the job always writes "INFA" as the owner.
By default, this check box is cleared.
This property is not available for jobs that have a PostgreSQL source.
Add Operation Transaction Id
Select this check box to add a metadata column that includes the source transaction ID in the output that the job propagates to the target for SQL operations.
For initial loads, the job always writes "1" as the ID.
By default, this check box is cleared.
Add Before Images
Select this check box to include UNDO data in the output that an incremental load job writes to the target.
For initial loads, the job writes nulls.
By default, this check box is cleared.

0 COMMENTS

We’d like to hear from you!