Hi @Garybary,
Quick clarification on how table update triggers actually behave, because this changes the answer significantly.
Table update triggers fire on data-changing operations only (writes, merges, updates, deletes). A standalone VACUUM does NO...
Hi Danish, good push-back. You are right that getTable in the Unity Catalog audit logs is metadata-only: it fires when a client resolves a table reference or inspects its schema/properties, not when rows are actually scanned.
If you want a signal tha...
Hi TENDK,
That is expected behavior and does not necessarily mean something is wrong. Here is what is happening:
When you run nslookup from inside a Databricks notebook, the notebook is executing on a cluster that sits inside the Databricks-managed V...
Hi excavator-matt,
Thanks for the follow-up and glad to hear you got Option C (PAT-based) working with Copilot and VSCode, and that you have moved to Claude Code with the official skills.
Regarding the issues with Options A and B:
Option A (OAuth U2M...
Hi @Anish_2,
Looking at your pipeline DAG, the issue is that you have two separate APPLY CHANGES INTO flows both targeting the same silver table (ag_vlc_hist), one from ag_swt_vlchistory_historical and one from ag_swt_vlchistory. When you define mult...
