Skip to main content
Last updated on

Vimeo connector limitations

Beta

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

The managed Vimeo connector in Lakeflow Connect ingests four tables, reads at most 364 days of audit log history, uses full refresh only for team data, and doesn't support SCD type 2.

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

  • The connector ingests four tables: teams, team_members, team_roles, and audit_logs. It doesn't ingest other Vimeo APIs or resources.
  • The teams, team_members, and team_roles tables are full refresh only. The connector reingests all records on every run.
  • The audit_logs table ingests events from at most the previous 364 days, just under Vimeo's 365-day limit. Vimeo doesn't make older audit events available through the API.
  • The connector reads data for a single team account owner, set by the account owner user ID on the connection. It doesn't ingest data across multiple owners in one pipeline.
  • SCD type 2 isn't supported for any table because every table has VARIANT columns, which the connector can't compare for row-level change tracking.
On this page