Oracle Eloqua connector limitations

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Oracle Eloqua from the Previews page. See Manage Azure Databricks previews.

The managed Oracle Eloqua connector in Lakeflow Connect reingests three tables in full on every run and doesn't capture records deleted from incremental tables until you run a full refresh.

General software as a service (SaaS) connector limitations

The limitations in this section apply to all SaaS connectors in Lakeflow Connect.

• When you run a scheduled pipeline, alerts don't trigger immediately. Instead, they trigger when the next update runs.
• When a source table is deleted, the destination table is not automatically deleted. You must delete the destination table manually. This behavior is not consistent with Spark Declarative Pipelines on Lakeflow behavior.
• During source maintenance periods, Databricks might not be able to access your data.
• If a source table name conflicts with an existing destination table name, the pipeline update fails.
• Multi-destination pipeline support is API-only.
• You can optionally rename a table that you ingest. If you rename a table in your pipeline, it becomes an API-only pipeline, and you can no longer edit the pipeline in the UI.
• If you select a column after a pipeline has already started, the connector does not automatically backfill data for the new column. To ingest historical data, manually run a full refresh on the table.
• Databricks can't ingest two or more tables with the same name in the same pipeline, even if they come from different source schemas.
• The source system assumes that the cursor columns are monotonically increasing.
• The connector ingests raw data without transformations. Use downstream Spark Declarative Pipelines on Lakeflow pipelines for transformations.

Connector-specific limitations

The limitations in this section apply to the Oracle Eloqua connector.

• Expect every pipeline run to reingest the option_list, event_registration_registrant, and custom_object tables in full. These tables don't support incremental ingestion, so each run reads all of their records from Oracle Eloqua, and the destination tables reflect inserts, updates, and deletes as of that run.
• Run a full refresh of an incremental table to remove records deleted in Oracle Eloqua. Incremental tables capture inserted and updated records only, so deleted records remain in the destination table until the next full refresh.