Skip to main content
DatabricksCustomer feedback

Databricks users discuss Materialized Views for Gold layer aggregates, praising automatic incremental serverless updates while noting limitations like unexpected full reloads and refactoring...

Source: Autobound Signal API · 172 signals tracked for Databricks · updated

Get Databricks' live signals in Claude or ChatGPT, or by API

AskWhat changed at Databricks this week? Use Autobound signals for databricks.com.

What happened

Databricks users discuss Materialized Views for Gold layer aggregates, praising automatic incremental serverless updates while noting limitations like unexpected full reloads and refactoring challenges.

Source

RedditNov 14, 2026By u/SalamanderOpen859

r/databricks

Are you using Databricks Materialized Views for your Gold layers yet? Thoughts?

upvotes
23
comments
17

Post

Highlighted: the lines this signal was extracted from

Hey everyone, I’ve been implementing Databricks Materialized Views for executive reporting (Gold layer aggregates like daily revenue summaries, customer 360 metrics, etc.) and wanted to see how others are using them in production. Historically, keeping summary tables up to date meant writing custom MERGE INTO scripts, managing orchestration dependencies, or dealing with sluggish standard views that re-scanned massive Delta tables on every query. Having the platform automatically handle incremental updates under the hood via serverless compute has been a massive time-saver. Curious to hear your experiences: Are you fully embracing Materialized Views for Gold layer reporting, or sticking to traditional Delta tables with custom upsert logic? Have you run into any gotchas regarding compute costs or refresh frequencies with larger datasets? How do they hold up when dealing with complex multi-table joins and apportioned aggregations?

Also quoted as evidence

  • [comment u/ninilich] MVs are the wrong tool for Gold. They are strictly not recommended for GOLD for enterprise-grade data platforms.

  • [comment u/Proud-Passion-3668] We're migrating our existing notebooks and orchestration to MVs and SDP. Our pipelines run faster, cheaper, and we don't need to handle the order of execution.

reddit.com/r/databricks/comments/1xw945t/are_you_using_databricks_mat...Read the full source

Comments on the post

5 of 17 comments
  • “They're great on the happy path but can be challenging to work with if refactoring and have a locked down environment. It can be tricky to move MVs to new pipelines without admin or drop+re-run. You cannot use cloning and can limit DR or other features. I believe there's a 16 pipeline at a time concurrency limit. Complex joins usually equals a full reload, so it can take some thinking to get incre”

    u/Significant_Win_72248 points · Nov 14, 2026View

  • “MVs are the wrong tool for Gold. They are strictly not recommended for GOLD for enterprise-grade data platforms. Only in specific cases ir make sence use them. Issues for Gold with MV: There are no real incremental updates. The Databricks engine can run a full refresh at any time. Your data for e.g. 2020 can be unexpectedly recalculated without your knowledge. Orchestration is uncontrolled”

    u/ninilich7 points · Nov 14, 2026View

  • “We're migrating our existing notebooks and orchestration to MVs and SDP. Our pipelines run faster, cheaper, and we don't need to handle the order of execution.”

    u/Proud-Passion-36684 points · Nov 14, 2026View

  • “I generally don't see many arguments anymore for using SDP, since Genie is able to write anything it needs for a data pipeline within a few minutes. Working that way is also some kind of declarative, but offers much more flexibility in the end.”

    u/Sea_Basil_65012 points · Nov 14, 2026View

  • “We use both MV and delta tables depending on the script. The reason we shifted few tables from MV to delta was there was a issue with incremental loading through time stamp filter, since MV resolves params and other things during runtime in our case it was defaulting to full refresh(purpose of MV was auto incremental but in our case was going for full refresh each time) hence converted such MVs in”

    u/Plane_Sector_85601 points · Nov 15, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/databricks
Event date
Nov 2026

The full record

From the Signal API record

Numbers

Mentions
18

Details

Timing
Ongoing state
Category
Features
Virality
Somewhat high
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • data engineering
  • performance
  • compute cost
  • etl

Flair

  • Discussion

Products named

  • Materialized Views
  • Delta Lake
  • SDP
  • Genie

Extraction

Sentiment
Mixed
Detected
Nov 14, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Databricks and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Databricks this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/b66255f8-7fc8-595b-a41e-94425b186990 returns this record as JSON. POST /v1/companies/enrich returns every signal for databricks.com.

{
  "signal_id": "b66255f8-7fc8-595b-a41e-94425b186990",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-11-14T18:11:19+00:00",
  "company": {
    "name": "Databricks",
    "domain": "databricks.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "data engineering",
      "etl",
      "performance",
      "compute cost"
    ],
    "post_id": "1xw945t",
    "summary": "Databricks users discuss Materialized Views for Gold layer aggregates, praising automatic incremental serverless updates while noting limitations like unexpected full reloads and refactoring challenges.",
    "category": "features",
    "comments": [
      {
        "url": "https://www.reddit.com/r/databricks/comments/1xw945t/comment/19smyvjt7zt7n/",
        "depth": 0,
        "score": 8,
        "author": "Significant_Win_7224",
        "excerpt": "They're great on the happy path but can be challenging to work with if refactoring and have a locked down environment. It can be tricky to move MVs to new pipelines without admin or drop+re-run. You cannot use cloning and can limit DR or other features. I believe there's a 16 pipeline at a time concurrency limit. Complex joins usually equals a full reload, so it can take some thinking to get incre",
        "posted_at": "2026-11-14T19:23:33.000Z",
        "author_url": "https://www.reddit.com/user/Significant_Win_7224/"
      },
      {
        "url": "https://www.reddit.com/r/databricks/comments/1xw945t/comment/19smzi964e17n/",
        "depth": 0,
        "score": 7,
        "author": "ninilich",
        "excerpt": "MVs are the wrong tool for Gold. They are strictly not recommended for GOLD for enterprise-grade data platforms. Only in specific cases ir make sence use them.\n\n Issues for Gold with MV:\n\n There are no real incremental updates. The Databricks engine can run a full refresh at any time.\n\n Your data for e.g. 2020 can be unexpectedly recalculated without your knowledge.\n\n Orchestration is uncontrolled",
        "posted_at": "2026-11-14T19:37:41.000Z",
        "author_url": "https://www.reddit.com/user/ninilich/"
      },
      {
        "url": "https://www.reddit.com/r/databricks/comments/1xw945t/comment/19sn8vq8xfo9u/",
        "depth": 0,
        "score": 4,
        "author": "Proud-Passion-3668",
        "excerpt": "We're migrating our existing notebooks and orchestration to MVs and SDP. Our pipelines run faster, cheaper, and we don't need to handle the order of execution.",
        "posted_at": "2026-11-14T23:07:52.000Z",
        "author_url": "https://www.reddit.com/user/Proud-Passion-3668/"
      },
      {
        "url": "https://www.reddit.com/r/databricks/comments/1xw945t/comment/19sn6vxm6qbab/",
        "depth": 0,
        "score": 2,
        "author": "Sea_Basil_6501",
        "excerpt": "I generally don't see many arguments anymore for using SDP, since Genie is able to write anything it needs for a data pipeline within a few minutes. Working that way is also some kind of declarative, but offers much more flexibility in the end.",
        "posted_at": "2026-11-14T22:23:09.000Z",
        "author_url": "https://www.reddit.com/user/Sea_Basil_6501/"
      },
      {
        "url": "https://www.reddit.com/r/databricks/comments/1xw945t/comment/19snkir1gx1gk/",
        "depth": 0,
        "score": 1,
        "author": "Plane_Sector_8560",
        "excerpt": "We use both MV and delta tables depending on the script. The reason we shifted few tables from MV to delta was there was a issue with incremental loading through time stamp filter, since MV resolves params and other things during runtime in our case it was defaulting to full refresh(purpose of MV was auto incremental but in our case was going for full refresh each time) hence converted such MVs in",
        "posted_at": "2026-11-15T03:28:49.000Z",
        "author_url": "https://www.reddit.com/user/Plane_Sector_8560/"
      }
    ],
    "evidence": [
      "[post] Having the platform automatically handle incremental updates under the hood via serverless compute has been a massive time-saver.",
      "[comment u/ninilich] MVs are the wrong tool for Gold. They are strictly not recommended for GOLD for enterprise-grade data platforms.",
      "[comment u/Proud-Passion-3668] We're migrating our existing notebooks and orchestration to MVs and SDP. Our pipelines run faster, cheaper, and we don't need to handle the order of execution."
    ],
    "virality": "somewhat_high",
    "post_date": "2026-11-14T18:11:19.000Z",
    "post_kind": "text",
    "post_text": "Hey everyone,\n\nI’ve been implementing Databricks Materialized Views for executive reporting (Gold layer aggregates like daily revenue summaries, customer 360 metrics, etc.) and wanted to see how others are using them in production.\n\nHistorically, keeping summary tables up to date meant writing custom MERGE INTO scripts, managing orchestration dependencies, or dealing with sluggish standard views that re-scanned massive Delta tables on every query.\n\nHaving the platform automatically handle incremental updates under the hood via serverless compute has been a massive time-saver.\n\nCurious to hear your experiences:\n\nAre you fully embracing Materialized Views for Gold layer reporting, or sticking to traditional Delta tables with custom upsert logic?\n\nHave you run into any gotchas regarding compute costs or refresh frequencies with larger datasets?\n\nHow do they hold up when dealing with complex multi-table joins and apportioned aggregations?",
    "sentiment": "mixed",
    "subreddit": "databricks",
    "event_date": "2026-11",
    "post_flair": [
      "Discussion"
    ],
    "post_title": "Are you using Databricks Materialized Views for your Gold layers yet? Thoughts?",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/databricks/comments/1xw945t/are_you_using_databricks_materialized_views_for/",
    "entity_role": "vendor",
    "post_author": "SalamanderOpen859",
    "upvote_ratio": 0.896551724137931,
    "mention_count": 18,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/databricks/",
    "total_upvotes": 23,
    "comments_total": 17,
    "total_comments": 17,
    "post_author_url": "https://www.reddit.com/user/SalamanderOpen859/",
    "signal_category": "feedback",
    "comments_included": 5,
    "products_mentioned": [
      "Materialized Views",
      "Delta Lake",
      "SDP",
      "Genie"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.