I am currently working on a Hive Metastore to Unity Catalog migration in Databricks. As part of this process, I need to upgrade several components, including workflows and clusters.

I would like guidance on the following:

UDF Dependency Identification: What is the best approach to identify dependencies associated with UDFs in the Hive Metastore? Are there specific tools, queries, or best practices for efficiently tracing these dependencies?

Migration and Compatibility Changes: What key changes should be applied to UDFs to ensure compatibility with Unity Catalog? Are there particular adjustments needed for path references, data access permissions, or function registration?

I am currently working on a Hive Metastore to Unity Catalog migration in Databricks. As part of this process, I need to upgrade several components, including workflows and clusters.

I would like guidance on the following:

UDF Dependency Identification: What is the best approach to identify dependencies associated with UDFs in the Hive Metastore? Are there specific tools, queries, or best practices for efficiently tracing these dependencies?

Migration and Compatibility Changes: What key changes should be applied to UDFs to ensure compatibility with Unity Catalog? Are there particular adjustments needed for path references, data access permissions, or function registration?

• pyspark
• databricks
• user-defined-functions
• azure-databricks
• databricks-unity-catalog

Share Improve this question Follow asked Mar 12 at 11:45 Shravan ShibuShravan Shibu 111 bronze badge 1

• can you provide the code what have you tried so far? – Dileep Raj Narayan Thumula Commented Mar 12 at 12:11

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 0

To move UDFs from the Hive metastore to Unity Catalog in Azure Databricks, you need to create the UDF in Unity Catalog first and then remove the old one from the Hive metastore.

First you need use the Databricks Runtime 14.1 or later Make sure unity Catalog enabled – Your Databricks workspace should already be set up with Unity Catalog. Storage setup – If you are migrating managed tables, you will need to set up storage credentials and external locations for your storage.

Also Know more about Manage privileges in Unity Catalog

Next You need to create a New UDF in Unity Catalog.

CREATE FUNCTION catalog.schema.udf_name
(parameter_name1 datatype1, parameter_name2 datatype2)
RETURNS datatype
LANGUAGE {language}
AS 'udf_code';

Managed tables in Unity Catalog are stored in a designated managed storage location. Because of this, if you want to copy existing Hive tables as managed tables in Unity Catalog, you will need to use CLONE or CREATE TABLE AS SELECT (CTAS).

Know more about the Hive to Unity Catalog migration options