Skip to main content
Last updated on

PayPal connector limitations

Beta

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

This page contains information about known limitations of the managed PayPal connector in Lakeflow Connect.

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 PayPal connector.

Deleted records​

  • The connector doesn't propagate deletes for the transaction and invoice tables. PayPal doesn't make deletes available for these records. Canceled invoices appear with status set to CANCELLED.

Incremental ingestion​

  • The balance, product, and billing_plan tables don't support incremental ingestion. Each pipeline run reingests all records for these tables.
  • The invoice table rereads every invoice on each sync, because PayPal can't filter invoices by update time. Only changed invoices are written to the destination table.
  • The transaction table doesn't capture changes made to a transaction more than 6 hours after it's initiated, such as a pending transaction that settles later. Schedule the pipeline to run at least every 6 hours.
  • Changes to an invoice's archived and viewed_by_recipient fields don't update any invoice timestamp, so the connector might not capture them until you run a full refresh.
On this page