Glean connector FAQ
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
This page answers frequently asked questions about the managed Glean ingestion connector in Lakeflow Connect. For FAQs that apply to all managed connectors, see Managed connector FAQs.
Which tables does the connector support?
The connector supports two source tables: insights, which contains company-wide Glean usage insights for search, Assistant, and agents, and shortcuts, which contains the shortcuts (go links) defined in your Glean deployment. For their schemas, see Supported source tables.
Is ingestion incremental?
No. The Glean insights and listshortcuts endpoints don't expose a cursor, so both tables are ingested as full-refresh snapshots. Each sync replaces the destination table with the latest data. See Glean connector limitations.
Does the connector keep historical snapshots?
No. Because both tables are full-refresh, each sync overwrites the destination table with the current state. To keep a daily history of insights, materialize the destination table downstream on your own schedule.
Which authentication method does the connector support?
The connector authenticates with a Glean Client API token, sent as an HTTP Bearer token. The token must carry both the Insights and Shortcuts scopes. OAuth U2M, OAuth M2M, and basic authentication aren't supported. See Configure authentication to Glean.