The Hive Metastore versions 1.2.2 and 2.2.0 are deprecated. You can no longer create services with these versions. Existing services will continue to function.
]]>Multi-region and custom dual region support for Dataproc Metastore is deprecated. You can no longer create new multi-region or custom dual region services. Existing services will continue to function.
]]>Backported HIVE-26882 to version 3.1.2. Hive Metastore now supports performing transactional checks of table parameters before altering a table.
Backported HIVE-28121 to version 3.1.2. Hive Metastore now uses direct SQL for transactionally altering table parameters.
]]>Dataproc Metastore multi-regional services now support the use of customer-managed encryption keys (CMEKs) -- (in preview).
]]>Dataproc Metastore federation now supports multi-regional Dataproc Metastore services.
]]>Dataproc Metastore supports custom region configurations. A custom region configuration lets your service run workloads from two separate regions.
]]>Dataproc Metastore managed migrations is generally available (GA)
Dataproc Metastore autoscaling is generally available (GA)
]]>Dataproc Metastore services can now enable deletion-protection to prevent the accidental removal of new or existing services.
]]>New Dataproc Metastore services configured with Private Service Connect can be connected from subnetworks of any region within the same VPC network.
Existing services configured with Private Service Connect do not inherit this change and continue to only support access from the VPC subnetworks that were specified during service creation.
]]>Dataproc Metastore now supports managed migrations.
Managed migration is an automated feature that helps you migrate data from a self-managed Hive Metastore to a Dataproc Metastore service, without any sizable down time.
Dataproc Metastore now supports autoscaling. Autoscaling automatically increases or decreases the scaling factor required to run your workloads.
]]>Dataproc Metastore now supports scheduled backups. Backups can be scheduled to run at user-specified cron job intervals, including running daily, weekly, or monthly.
]]>The Data Catalog Sync feature is generally available (GA). With this launch, Data Catalog also now supports syncing metadata from Dataproc Metastore services using the Spanner Database.
]]>Dataproc Metastore is available in the following multi-regional configurations, nam11 and eur5.
Dataproc Metastore is now available in the me-central2 (Dammam) region. For more information, see Dataproc Metastore locations.
Dataproc Metastore now supports multi-regional configurations.
]]>Dataproc Metastore gRPC endpoints are generally available (GA).
Metadata federation support for BigQuery and BigLake is generally available (GA).
]]>Administrator interface is generally available (GA). The GA release adds support for altering Hive table properties.
]]>Metadata federation now supports Dataplex lakes as a metadata source (in preview)
]]>Dataproc Metastore 2 is now Generally Available (GA). Dataproc Metastore 2 provides horizontal scalability through fine grained scaling options. For more information, see Datproc Metastore versions.
The Spanner database type is generally available (GA).
Auxiliary versions is generally available (GA).
]]>Dataproc Metastore is available in the following regions: asia-east2 (Hong Kong), europe-central2 (Warsaw), europe-north1 (Finland), and us-west4 (Las Vagas). For more information, see Dataproc Metastore locations.
]]>Dataproc Metastore administrator interface is available in preview.
The administrator interface provides you with a centralized tool to inspect and manage the metadata stored in your Dataproc Metastore service.
]]>Metadata federation now supports BigQuery datasets as a metadata source (in preview).
]]>Dataproc Metastore is available in the following regions: us-west2 (Los Angeles), us-west3 (Salt Lake City), europe-west4 (Netherlands), europe-west6 (Zürich), and asia-east1 (Taiwan). For more information, see Dataproc Metastore locations.
Note that these services are immediately available through the gcloud CLI and the REST API. Cloud console availability will vary by region over the next few weeks.
]]>Metadata federation is generally available (GA).
Metadata federation lets you access metadata that is stored in multiple Dataproc Metastore instances.
To set up a federation, you create a federation service and then configure multiple Dataproc Metastore instances as your backend metastores. The federation service then exposes a single gRPC endpoint, which you can use to access metadata across all of your metastore instances.
Private Service Connect for Dataproc Metastore is generally available (GA).
]]>Updated Dataproc Metastore auxiliary versions to support the Spanner database type.
]]>gRPC endpoint protocol is available in Preview.
]]>Fixed the issue causing metadata batch sync from Dataproc Metastore to Data Catalog to not work.
]]>Fixed the issue causing Dataproc Metastore service creation to fail with the error NO_MATCHING_ACCESS_LEVEL due to a known issue where dns.googleapis.com is in the service perimeter but not in the allowlist.
Performing import, export, backup, or restore on Spanner-backed services now returns a 4XX error since these operations aren't supported.
Added additional mutual exclusion validation for Data Catalog and Spanner-backed services.
v1Fixed the issue causing request_count metric spikes due to a bug in the logic of our metrics reporting pipeline.
Data Catalog sync users must request roles/metastore.metadataViewer to view synced Dataproc Metastore entries in Data Catalog. The roles/metastore.Admin and roles/metastore.Editor no longer support metastore databases and tables permissions.
Creating a Dataproc Metastore service results in the error NO_MATCHING_ACCESS_LEVEL due to dns.googleapis.com in the service perimeter but not in the allowlist. To work around this issue, remove dns.googleapis.com from the perimeter during API calls.
The request_count metric spikes due to a bug in the logic of our metrics reporting pipeline.