Ingest data from Vimeo
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.
Create a managed Vimeo ingestion pipeline in Lakeflow Connect using the Databricks UI, Declarative Automation Bundles, or a Databricks notebook. The pipeline ingests the teams, team_members, team_roles, and audit_logs tables into Unity Catalog.
Requirements
-
To create an ingestion pipeline, first meet the following requirements:
-
Your workspace must be enabled for Unity Catalog.
-
Serverless compute must be enabled for your workspace. See Serverless compute requirements.
-
To create a new connection, you must have
CREATE CONNECTIONprivileges on the metastore. See Manage privileges in Unity Catalog.If the connector supports UI-based pipeline authoring, an admin can create the connection and the pipeline at the same time by completing the steps on this page. However, if the users who create pipelines use API-based pipeline authoring or are non-admin users, an admin must first create the connection in Catalog Explorer. See Connect to managed ingestion sources.
-
To use an existing connection, you must have
USE CONNECTIONprivileges orALL PRIVILEGESon the connection object. -
You must have
USE CATALOGprivileges on the target catalog. -
You must have
USE SCHEMAandCREATE TABLEprivileges on an existing schema orCREATE SCHEMAprivileges on the target catalog.
-
-
To ingest from Vimeo, first configure authentication from Databricks and create a connection. See Configure authentication to Vimeo and Create a Vimeo connection.
Connector options
Set the pipeline-scoped start_datetime option in source_configurations to choose where the first audit_logs sync starts. For the option's details, see Connector options. For usage, see Examples.
Create an ingestion pipeline
For the list of supported source tables, see Supported source tables.
- Databricks UI
- Declarative Automation Bundles
- Databricks notebook
- In the sidebar of the Databricks workspace, click Data Ingestion.
- On the Add data page, under Databricks connectors, click Vimeo.
- On the Connection page of the ingestion wizard, select the connection that stores your Vimeo credentials. If you have the
CREATE CONNECTIONprivilege on the metastore, clickCreate connection to create a connection with the credentials from Configure authentication to Vimeo.
- Click Next.
- On the Ingestion setup page, enter a name for the pipeline.
- Select a catalog and a schema to write event logs to. If you have
USE CATALOGandCREATE SCHEMAprivileges on the catalog, clickCreate schema in the drop-down menu to create a schema.
- Click Create pipeline and continue.
- On the Source page, select the tables to ingest.
- Click Save and continue.
- On the Destination page, select a catalog and a schema to load data into. If you have
USE CATALOGandCREATE SCHEMAprivileges on the catalog, clickCreate schema in the drop-down menu to create a schema.
- Click Save and continue.
- (Optional) On the Schedules and notifications page, click
Create schedule. Set the frequency to refresh the destination tables.
- (Optional) Click
Add notification to set email notifications for pipeline operation success or failure, then click Save and run pipeline.
Use Declarative Automation Bundles to manage Vimeo pipelines as code. Bundles can contain YAML definitions of jobs and tasks, are managed using the Databricks CLI, and can be shared and run in different target workspaces (such as development, staging, and production). For more information, see What are Declarative Automation Bundles?.
-
Create a bundle using the Databricks CLI:
Bashdatabricks bundle init -
Add two new resource files to the bundle:
- A pipeline definition file (for example,
resources/vimeo_pipeline.yml). See pipeline.ingestion_definition and Examples. - A job definition file that controls the frequency of data ingestion (for example,
resources/vimeo_job.yml).
- A pipeline definition file (for example,
-
Deploy the pipeline using the Databricks CLI:
Bashdatabricks bundle deploy
-
Import the following notebook into your Databricks workspace:
-
Leave cells one and two as they are. Do not modify.
-
Modify cell three with your pipeline configuration details. See pipeline.ingestion_definition and Examples.
-
Optionally configure advanced pipeline settings. See Common patterns for managed ingestion pipelines.
-
Click Run all.
Examples
The Vimeo connector makes available 4 source tables in the default source schema. Ingest individual tables or the entire schema.
Ingest specific tables
Use this option to ingest a specific subset of tables, or to customize destination naming per table.
- Declarative Automation Bundles
- Databricks notebook
The following pipeline definition file ingests individual Vimeo tables:
resources:
pipelines:
vimeo_pipeline:
name: vimeo_pipeline
catalog: 'main'
target: 'vimeo_data'
ingestion_definition:
connection_name: vimeo_connection
source_configurations:
- api_source_connector_config:
configs:
start_datetime: '<start-date>'
objects:
- table:
source_schema: 'default'
source_table: 'teams'
destination_catalog: 'main'
destination_schema: 'vimeo_data'
destination_table: 'teams'
- table:
source_schema: 'default'
source_table: 'team_members'
destination_catalog: 'main'
destination_schema: 'vimeo_data'
destination_table: 'team_members'
- table:
source_schema: 'default'
source_table: 'team_roles'
destination_catalog: 'main'
destination_schema: 'vimeo_data'
destination_table: 'team_roles'
- table:
source_schema: 'default'
source_table: 'audit_logs'
destination_catalog: 'main'
destination_schema: 'vimeo_data'
destination_table: 'audit_logs'
The following pipeline specification ingests individual Vimeo tables:
pipeline_name = "vimeo_pipeline"
connection_name = "<vimeo-connection>"
pipeline_spec = {
"name": pipeline_name,
"ingestion_definition": {
"connection_name": connection_name,
"source_configurations": [
{
"api_source_connector_config": {
"configs": {
"start_datetime": "<start-date>"
}
}
}
],
"objects": [
{
"table": {
"source_schema": "default",
"source_table": "teams",
"destination_catalog": "main",
"destination_schema": "vimeo_data",
"destination_table": "teams"
}
},
{
"table": {
"source_schema": "default",
"source_table": "team_members",
"destination_catalog": "main",
"destination_schema": "vimeo_data",
"destination_table": "team_members"
}
},
{
"table": {
"source_schema": "default",
"source_table": "team_roles",
"destination_catalog": "main",
"destination_schema": "vimeo_data",
"destination_table": "team_roles"
}
},
{
"table": {
"source_schema": "default",
"source_table": "audit_logs",
"destination_catalog": "main",
"destination_schema": "vimeo_data",
"destination_table": "audit_logs"
}
}
]
}
}
json_payload = json.dumps(pipeline_spec, indent=2)
create_pipeline(json_payload)
Ingest the entire schema
Use this option to ingest all Vimeo source tables into a single destination schema with one declaration.
- Declarative Automation Bundles
- Databricks notebook
The following pipeline definition file ingests all supported Vimeo tables into a destination schema:
resources:
pipelines:
vimeo_pipeline:
name: vimeo_pipeline
catalog: 'main'
target: 'vimeo_data'
ingestion_definition:
connection_name: vimeo_connection
source_configurations:
- api_source_connector_config:
configs:
start_datetime: '<start-date>'
objects:
- schema:
source_schema: 'default'
destination_catalog: 'main'
destination_schema: 'vimeo_data'
The following pipeline specification ingests all supported Vimeo tables into a destination schema:
pipeline_name = "vimeo_pipeline"
connection_name = "<vimeo-connection>"
pipeline_spec = {
"name": pipeline_name,
"ingestion_definition": {
"connection_name": connection_name,
"source_configurations": [
{
"api_source_connector_config": {
"configs": {
"start_datetime": "<start-date>"
}
}
}
],
"objects": [
{
"schema": {
"source_schema": "default",
"destination_catalog": "main",
"destination_schema": "vimeo_data"
}
}
]
}
}
json_payload = json.dumps(pipeline_spec, indent=2)
create_pipeline(json_payload)
Declarative Automation Bundles job definition file
The following is an example job definition file for use with Declarative Automation Bundles. The job runs daily.
- Declarative Automation Bundles
resources:
jobs:
vimeo_job:
name: vimeo_job
schedule:
quartz_cron_expression: '0 0 0 * * ?'
timezone_id: 'UTC'
tasks:
- task_key: vimeo_ingestion
pipeline_task:
pipeline_id: ${resources.pipelines.vimeo_pipeline.id}
Common patterns
For advanced pipeline configurations, see Common patterns for managed ingestion pipelines.
Next steps
Start, schedule, and set alerts on your pipeline. See Common pipeline maintenance tasks.