Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.
The managed Google Drive connector in Lakeflow Connect allows you to ingest files from Google Drive into Azure Databricks. Ingest unstructured files as binary data, parse structured formats (CSV, JSON, XML, EXCEL, and more) into Delta tables, or capture file metadata without loading file contents.
For the standard Google Drive connector that uses Spark reader APIs (read_files, spark.read, Auto Loader), see Ingest files from Google Drive.
What to know before you start
| Topic | Why it matters |
|---|---|
| Azure Databricks user persona | The workflow depends on your Azure Databricks user persona:
|
| Authentication method | The steps to create a connection depend on the authentication method you select. |
| Interface | The steps to create a pipeline depend on the interface. |
| Ingestion frequency | The pipeline schedule depends on your latency and cost requirements. |
| Common patterns | Depending on your ingestion needs, the pipeline might use configurations like history tracking, column selection, and row filtering. Supported configurations vary by connector. See Feature availability. |
Start ingesting from Google Drive
The following table has an overview of the end-to-end Google Drive ingestion flow, based on user type:
| User | Steps |
|---|---|
| Administrator |
|
| Non-administrator | Use any supported interface to create a pipeline from an existing connection. See Ingest data from Google Drive. |
Feature availability
| Feature | Availability |
|---|---|
| UI-based pipeline authoring | |
| API-based pipeline authoring | |
| Declarative Automation Bundles | |
| Incremental ingestion | |
| Unity Catalog governance | |
| Orchestration using Databricks Workflows | |
| SCD type 2 | |
| Schema evolution | Configurable via schema_evolution_mode. See Google Drive connector reference. |
| API-based column selection and deselection | |
| API-based row filtering |
Authentication methods
| Authentication method | Availability |
|---|---|
| OAuth U2M | |
| OAuth M2M | |
| OAuth (manual refresh token) | |
| Basic authentication (username/password) | |
| Basic authentication (API key) | |
| Basic authentication (service account JSON key) |