Skip to main content
Last updated on

Notion connector limitations

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page by opting into the Notion connector preview. See Manage Databricks previews.

This page contains information about known limitations of the managed Notion 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 Notion connector.

  • The connector ingests nested fields that hold arbitrary user-defined content as a JSON-encoded STRING. Some fields in the Notion schema are nested within complex structures whose inner fields vary by object. To keep the destination schema consistent, the connector represents these fields as a STRING containing JSON.
  • The users, page_comments, block_comments, blocks, and databases tables support full refresh only. Notion exposes no change-time ordering for these endpoints, so the connector re-scans them in full on each pipeline update. For the sync mode of each table, see Supported source tables.
  • Notion page permissions (ACLs) are not synced. Who can view a page within Notion is not reflected in the ingested data.
  • Deeply nested blocks are ingested only up to a fixed nesting depth. The connector builds the blocks table by recursively walking the block tree, and recursion is bounded at 30 levels by default. Blocks nested deeper than this limit are not ingested.
  • The connector ingests only the pages and data sources that you share with the integration in the Notion page picker during connection setup. Content that is not shared is not ingested. See Create a Notion connection.
On this page