Question 2: Legacy Hive Metastore Support Timeline

Question

Question 2: Legacy Hive Metastore Support Timeline

Mahale, Saurav 0

Starting September 30, 2026, new Databricks workspaces will be provisioned with Unity Catalog and without certain legacy features.

For existing workspaces, what is the official Databricks support timeline/end-of-support date for the legacy Hive Metastore?

Specifically:

Until what date can existing Production workspaces continue using the legacy Hive Metastore?
Will existing workspaces be automatically migrated or converted to Unity Catalog?
Will the legacy Hive Metastore remain available as a fallback after migrating the workspace to Unity Catalog?
Are there any planned dates when direct access to hive_metastore will be completely removed?

We would like to understand the recommended approach for maintaining a safe rollback/fallback option during our Production migration.

SIVASANKAR YEDDULA 165 Reputation points Microsoft External Staff Moderator

2026-08-27T17:33:15.0533333+00:00

Hi @Mahale, Saurav ,

According to the current Azure Databricks documentation, the September 30, 2026 change applies only to newly created workspaces. Existing workspaces and their current workloads are explicitly stated as not being impacted by this change.

Regarding your specific questions:

Until what date can existing Production workspaces continue using the legacy Hive Metastore

At this time, Databricks has not published an official end-of-support or removal date for the legacy Hive Metastore in existing workspaces. Existing workspaces can continue using the legacy Hive Metastore, and the September 30, 2026 deadline does not apply to them.

Will existing workspaces be automatically migrated or converted to Unity Catalog

Based on the current documentation, Databricks does not automatically migrate existing workspaces to Unity Catalog. Databricks recommends migrating existing workspaces to Unity Catalog, but the migration remains a customer-managed activity.

Will the legacy Hive Metastore remain available as a fallback after migrating the workspace to Unity Catalog

Yes. Databricks documentation states that Unity Catalog can coexist with the legacy Hive Metastore. After enabling Unity Catalog, the legacy metastore continues to be accessible through the hive_metastore catalog unless access is explicitly disabled. This allows organizations to use a phased migration approach and maintain a fallback path during migration activities.

Are there any planned dates when direct access to hive_metastore will be completely removed

As of the current published documentation, Databricks has not announced a date for the complete removal of direct access to hive_metastore in existing workspaces. While Databricks recommends migrating workloads and data to Unity Catalog, no public retirement date has been documented.

Recommended migration approach

For Production environments, Databricks recommends a gradual migration strategy:

Enable Unity Catalog.

Migrate tables and workloads incrementally.

Continue accessing legacy objects through the hive_metastore catalog during the transition period.

Validate permissions, workloads, and governance controls in Unity Catalog before decommissioning legacy dependencies.

Treat the legacy Hive Metastore as a temporary compatibility layer while planning full migration to Unity Catalog.

In summary, based on current documentation, there is no published end-of-support date for the legacy Hive Metastore in existing workspaces, no automatic migration, and no announced date for complete removal of hive_metastore access. Existing workspaces remain supported, although Databricks strongly recommends planning and executing a migration to Unity Catalog.

If this answer helped, please consider accepting it so it can assist other community members with similar migration planning questions.
SIVASANKAR YEDDULA 165 Reputation points Microsoft External Staff Moderator

2026-08-31T10:32:20.9533333+00:00

Hi @Mahale, Saurav ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.
SIVASANKAR YEDDULA 165 Reputation points Microsoft External Staff Moderator

2026-09-01T01:51:06.5266667+00:00

Hi @Mahale, Saurav ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well

2 answers

Your answer

SIVASANKAR YEDDULA 165 Reputation points Microsoft External Staff Moderator

2026-08-31T10:32:20.9533333+00:00

Hi @Mahale, Saurav ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.
SIVASANKAR YEDDULA 165 Reputation points Microsoft External Staff Moderator

2026-09-01T01:51:06.5266667+00:00

Hi @Mahale, Saurav ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well

Answer 1

The current documentation answers part of the question directly, but it is important to separate what Databricks has officially announced from what has not been announced.

Starting September 26, new workspaces will be provisioned without access to certain legacy features, including the legacy Hive Metastore. However, Databricks explicitly states that existing workspaces and their workflows are not impacted by this change. Therefore, this date should not be interpreted as an end-of-support or shutdown date for Hive Metastore in existing production workspaces. (Azure Databricks documentation)

With respect to the specific questions:

How long can existing production workspaces continue using Hive Metastore?

Based on the currently published documentation, Databricks has not announced an end-of-support date, retirement date, or removal date for Hive Metastore in existing workspaces. The September 30, 2026 milestone applies to the provisioning of new workspaces, not the operation of existing ones.

Will existing workspaces be automatically converted to Unity Catalog?

I could not find any documentation indicating automatic migration. Databricks recommends that customers migrate to Unity Catalog, but the migration process remains customer-managed and requires planning, validation, and execution by workspace administrators.

Can Hive Metastore still be used after enabling Unity Catalog?

Yes. Databricks documentation describes Unity Catalog as an additive governance layer. In Unity Catalog-enabled workspaces, the legacy Hive Metastore can still be accessed through the hive_metastore catalog. Databricks also documents migration approaches that allow both environments to coexist during transition periods. (Work with Hive Metastore alongside Unity Catalog)

Is there a published date for complete removal of hive_metastore access?

I could not find any official Databricks announcement that specifies a date when direct access to hive_metastore will be removed from existing workspaces. Current documentation continues to describe coexistence and migration scenarios, while recommending eventual migration away from the legacy model.

Migration and rollback considerations

One practical point for production migrations is that Databricks currently supports a phased transition model. Unity Catalog can be introduced while existing Hive Metastore assets remain available, allowing teams to validate governance, permissions, workloads, and operational processes before removing legacy dependencies.

Databricks also documents Hive Metastore Federation as a migration option for organisations that want a gradual transition path instead of a large-scale cutover. The key objective should be to use Hive Metastore as a temporary compatibility mechanism during migration rather than as a long-term governance strategy.

To sum-up, the published September 30, 2026 date is a new-workspace provisioning change, not a documented retirement date for Hive Metastore in existing workspaces. As of the current documentation, there is no announced end-of-support date, no automatic migration requirement, and no published date for complete removal of hive_metastore access in existing workspaces.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

Answer 2

The documented date is September 30, 2026 for a change to new workspaces only: new workspaces will be provisioned with Unity Catalog and without access to certain legacy features, including the legacy Hive metastore. The documentation explicitly states that existing workspaces and their workflows are not impacted by that change.

From the provided documentation, there is no official end-of-support or removal date stated for the legacy Hive metastore in existing workspaces.

Based on the documented guidance:

Existing Production workspaces can continue using the legacy Hive metastore beyond September 30, 2026, because that date applies to new workspaces, and existing workspaces are stated as not impacted.
Existing workspaces are not described as being automatically migrated or converted to Unity Catalog. The guidance is to prepare and migrate, and Databricks recommends upgrading existing workspaces to Unity Catalog, but the migration is not described as automatic.
After migrating to Unity Catalog, the legacy Hive metastore can still remain accessible unless access is explicitly disabled. By default, compute clusters continue to connect to the Hive metastore even after migration unless Hive metastore access is explicitly disabled.
There is no documented date in the provided sources when direct access to hive_metastore will be completely removed for existing workspaces.

For fallback during Production migration, the documented model is:

Use a hybrid workspace during transition, where Hive metastore objects continue to appear in the hive_metastore catalog alongside Unity Catalog.
Migrate tables and workloads to Unity Catalog.
Keep in mind this is a legacy workflow and does not provide the full governance capabilities of Unity Catalog.
Only disable direct Hive metastore access after migration validation, because access is not disabled automatically.

Databricks’ documented recommendation is to migrate off the legacy Hive metastore to Unity Catalog as soon as practical. The two documented migration paths are:

Upgrade all Hive metastore tables to Unity Catalog.
Use Hive metastore federation to create a more gradual transition path.