Discover · databricks.com

No picture published by databricks.com

Change data feed on materialized views (Beta)

docs.databricks.com databricks.com

This is what was read here when it was published. databricks.com no longer carries it in what it publishes now.

You can now read a change data feed from a materialized view created in a Lakeflow pipeline or in Databricks SQL, using Databricks Runtime 18 LTS or above. Use this to replicate materialized view changes to destinations outside Databricks, or to keep a history of materialized view changes for auditing and reporting. Materialized views use automatic change data feed, so the change data feed is available for any materialized view with row tracking enabled, without configuring each materialized view. This feature is in Beta.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Change — person

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

More like this

Also from docs.databricks.com

  1. Genie Code analysis for alerts is in Betadatabricks.com
  2. MCP tools in Genie Agents are generally availabledatabricks.com
  3. Lakebase now available in three additional regionsdatabricks.com
  4. Warehouse-level statement timeouts are now generally availabledatabricks.com
  5. OAuth authentication for webhook destinations will soon be available by default for workspaces with the compliance security profile enableddatabricks.com
  6. The Databricks GitHub app will request permission to create and manage pull requestsdatabricks.com