Skip to main content
Last updated on

Google Search Console connector limitations

Beta

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

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

  • The sites and sitemaps tables do not support incremental ingestion. The connector performs a full refresh on every pipeline update.
  • Google Search Console Search Analytics data has an approximate delay of two to four days. Data for recent dates might not appear in the first sync after pipeline creation.
  • The data_state connector option applies only to daily search analytics tables. The hourly tables always use the hourly_all data state.
  • Hourly search analytics data is available only for properties using the web and googleNews search types. The news, image, and video search types are not supported for hourly tables.
  • The connector ingests up to 500 days of historical data on the first sync, measured from the date the first pipeline update runs. Use the start_date connector option to limit the initial lookback window.
On this page