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

Guidelines for Amazon Redshift targets

Guidelines for Amazon Redshift targets

Consider the following guidelines when you use Amazon Redshift targets:
  • Before writing data to Amazon Redshift target tables,
    application ingestion
    jobs stage the data in an Amazon S3 bucket. You must specify the name of the bucket when you configure the
    application ingestion
    task. The ingestion jobs use the COPY command to load the data from the Amazon S3 bucket to the Amazon Redshift target tables. For more information about the COPY command, see the Amazon Web Services documentation.
  • When you define a connection for an Amazon Redshift target, provide the access key and secret access key for the Amazon S3 bucket in which you want the
    application ingestion
    jobs to stage the data before loading it to the Amazon Redshift target tables.
  • When you ingest data from a source to an Amazon Redshift target, the
    application ingestion
    job fails if the data source contains more than 32 data fields or columns that are defined as primary keys.
  • Incremental load jobs and combined initial and incremental load jobs generate a recovery table named INFORMATICA_CDC_RECOVERY on the target to store internal service information. The data in the recovery table prevents the jobs that are restarted after a failure from propagating previously processed data again. The recovery table is generated in the schema of the target tables.

0 COMMENTS

We’d like to hear from you!