Google Drive Audit Logs connector limitations

Important

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.

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

• The connector makes available a single source table, drive. It doesn't make available other Google Workspace audit activity applications or reports. For details, see Supported source tables.
• SCD Type 2 isn't supported. The drive table has VARIANT columns, and Drive audit events are append-only.
• The Google Workspace Admin SDK Reports API retains Drive audit activity for up to 180 days. The connector can't ingest events older than the source retention window.
• Without a configured start datetime, the connector backfills the previous 180 days of Drive audit activity by default.