Google Workspace connector limitations

Important

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

The managed Google Workspace connector in Lakeflow Connect has the following known limitations.

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 Google Workspace connector.

• The connector ingests audit activity from the Admin SDK Reports API. It doesn't ingest other Google Workspace API resources.
• SCD Type 2 isn't supported. Activity records have VARIANT columns, and audit events are append-only.
• Google Workspace retains activity logs for up to 180 days. The connector can't ingest events older than this retention window.
• Different Google Workspace applications report with different lag windows. Per-application lookback is applied to accommodate this lag. In particular, the takeout application's "process finished" event can lag by up to several days; very large exports finishing beyond the per-application lookback window may not be captured.
• On the first sync, the connector backfills the previous 179 days of audit activity.