Thanks for the detailed write-up. Short answer: your workflow is possible, but installing/running Lakebridge from a Databricks serverless web terminal is not the recommended path today.
The error you’re seeing happens because Lakebridge installation ...
Thanks for raising this. Based on the current public documentation, Unity AI Gateway’s documented OpenTelemetry path for coding-agent telemetry is to Databricks-managed Unity Catalog Delta tables, rather than to an arbitrary external OTel collector.
...
Thanks for reporting this — and for the thorough investigation you've already done (confirming no IS NULL matches and no is_variant_null hits).
What's likely happening:
When OPTIMIZE compacts files, it re-validates constraints against the data in the...
Thanks for sharing the screenshots. Assuming this is Lakebase Change Data Feed (formerly Lakehouse Sync) from Lakebase Postgres into Unity Catalog lb_*_history tables, this does not look like expected steady-state behavior.
A few things stand out:
O...
Databricks doesn’t expose a “DBU/hour per node type” lookup in system tables, but you can derive it empirically by dividing total DBUs recorded in the billable usage system table by total node runtime from the compute node timeline for each instance ...
