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

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

Mock connectors

Mock connectors

Mass Ingestion Databases
supports mock, or sample, connections for some of the sources and targets. Use mock connections to learn how to create initial load database ingestion tasks without creating real connections to the database.
A mock connector does not connect to a real database. Instead, a source mock connector uses flat files with sample data. A target mock connector reports the information about processed source data to
Mass Ingestion Databases
user interface, but it does not write any data to the target.
The sample connections appear in the source and target connection lists in Mass Ingestion Databases if you have the MockConnector license.
The following table lists mock connections that you can use for Mass Ingestion Databases sources and targets:
Connection name
Source or Target
Sample Oracle Connection
Source
Sample SQL Server Connection
Source
Sample S3 Connection
Target
Sample ADLS Gen2 Connection
Target
You must use sample connections for both the source and target databases. You cannot use a sample connection for only one of them, for example, for the source but not for the target.

Source data

The source data for sample connections is stored in CVS files in the following directory:
Secure_Agent_installation
/downloads/package-MockConnector.
version
/package/sampleData/source/
database_type
/
Each file represents a single table. A mock table name matches the file name. The first line in a file determines column headers, and the subsequent lines contain row data.

0 COMMENTS

We’d like to hear from you!