- biGENIUS-X Knowledge Base
- Generators
- Properties
-
Getting Started
-
General Overview
-
Application Modules
- Administration
- Global Features
- Solutions
- Projects
- Branches
- Source Systems
- Dataflow Modeling - Overview
- Dataflow Modeling - Wizard Steps
- Dataflow Modeling - Terms
- Dataflow Modeling - Term Mapping
- Dataflow Modeling - Relationships
- Relationship Modeling
- Generate Artifacts
- Project Settings
- Data Marketplace
-
Generators
-
Discovery application
-
Best Practices
-
FAQs
-
Product Release Notes
-
Legal Documents
Unity Catalog (Project)
Description
The Unity Catalog Property is available in Project Settings only for Projects configured with the Generator Spark with Databricks.
It indicates if Databricks Unity Catalog will be used or not.
The usage of Unity Catalog means no creation of databases and schemas through code:
- Table and views are created inside the catalog
- In contrast to the Hive catalog, where the object identifiers only consist of database.object_name, with the Unity catalog, the object identifiers look the same as for other database systems: database.schema.object_name. Therefore, in the replacement_config.json, the schema key always has to be specified, but for Hive usage, it has to be empty. The schema will be removed from the object identifier during the replacement.
Format
The Unity Catalog is a Boolean.
Example:
Default Value
The default value is False.