<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Dataproc Metastore API Changes — Google Cloud Radar</title>
  <subtitle>Real-time pre-release intelligence and changelog for Google Dataproc Metastore. Tracked from Google Discovery Service.</subtitle>
  <link href="https://google-cloud-radar.com/services/dataproc-metastore/atom.xml" rel="self" type="application/atom+xml" />
  <link href="https://google-cloud-radar.com/services/dataproc-metastore" rel="alternate" type="text/html" />
  <id>https://google-cloud-radar.com/services/dataproc-metastore/atom.xml</id>
  <updated>2026-09-23T00:00:00Z</updated>
  <author>
    <name>Google Cloud Radar</name>
    <uri>https://github.com/max-ostapenko/google-cloud-radar</uri>
  </author>
  
  <entry>
    <title>⚠️ [BREAKING] Lakehouse Proxy Config Introduced (Breaking)</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1beta</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">Dataproc Metastore now exposes `LakehouseProxyConfig` for managing phased migrations to Lakehouse Iceberg REST Catalogs. This new configuration and its properties are read-only, which is a breaking change for any clients attempting to write to them.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Metastore v1alpha: Lakehouse Proxy Config &amp; Read-Only Fields</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1alpha</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">The Metastore v1alpha API introduces Lakehouse proxy configuration for phased namespace migrations. The new &apos;lakehouseProxyConfig&apos; field in the Service schema and its sub-properties are now explicitly read-only, which is a breaking change.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] Lakehouse Proxy Routing &amp; Read-Only Config</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-23-metastore-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-23-metastore-v1</id>
    <published>2026-09-23T00:00:00Z</published>
    <updated>2026-09-23T00:00:00Z</updated>
    <summary type="text">Dataproc Metastore introduces new Lakehouse proxy routing capabilities for phased migrations to Iceberg REST Catalogs. The new `LakehouseProxyConfig` and its properties are now officially read-only, which is a breaking change if you were previously attempting to configure them.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary endTime is now read-only</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1beta" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1beta</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">A breaking change in the Metastore v1beta API marks the MigrationSummary endTime field as read-only. The createTime field description has also been updated to clarify its role in the migration process.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1beta" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary timestamps updated in Metastore v1alpha</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1alpha" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1alpha</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">The MigrationSummary schema now marks endTime as read-only and redefines createTime to reflect the start of metadata reads.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1alpha" />
  </entry>
  <entry>
    <title>⚠️ [BREAKING] MigrationSummary schema updates and breaking changes</title>
    <link href="https://google-cloud-radar.com/changes/2026-09-16-metastore-v1" rel="alternate" type="text/html" />
    <id>https://google-cloud-radar.com/changes/2026-09-16-metastore-v1</id>
    <published>2026-09-16T00:00:00Z</published>
    <updated>2026-09-16T00:00:00Z</updated>
    <summary type="text">The MigrationSummary schema has been updated with a new read-only endTime field and revised semantics for createTime.</summary>
    <category term="Data Analytics" />
    <category term="Dataproc Metastore" />
    <category term="metastore.v1" />
  </entry>
</feed>