USER MANUALS

Catalogs

Catalogs in the Denodo Embedded MPP are the equivalent to data sources in Denodo Virtual Dataport.

The Denodo Embedded MPP is distributed with three predefined catalogs:

Note

hive, delta and iceberg are used only by Denodo to create tables as a result of graphical exploration of datasets on the From object storage tab of the Embedded MPP data source.

Therefore hive, delta and iceberg are restricted catalogs, so they are not listed on the From MPP Catalogs tab of the Embedded MPP data source.

It is possible to define new catalogs. The recommended ways is using the presto.catalog property in values.yaml. These new catalogs will be accessed from the From MPP Catalogs tab.

Additional catalogs in From MPP Catalogs

Additional catalogs in From MPP Catalogs

See below for an example of an Iceberg catalog connected to the AWS Glue Data Catalog named glue-iceberg:

  # -- Additional catalogs
  catalog:
    #glue-iceberg: |-
    #  connector.name=iceberg
    #  iceberg.catalog.type=HIVE
    #  hive.metastore=glue
    #  hive.metastore.glue.region=xxx
    #  hive.metastore.glue.catalogid=yyy
    #  hive.metastore.glue.aws-access-key=abc
    #  hive.metastore.glue.aws-secret-key=xyz
    #  hive.config.resources=core-site.xml
    #  hive.parquet-batch-read-optimization-enabled=true

You can also define new catalogs creating a properties file in presto/conf/catalog/, e.g., presto/conf/catalog/glue_iceberg.properties. Although it is preferred to define new catalogs in values.yaml to facilitate version upgrades and management of environment-specific configurations.

Below there is an example of an Iceberg catalog to connect to AWS Glue Data Catalog:

connector.name=iceberg

hive.metastore=glue

# AWS region of the Glue Catalog
hive.metastore.glue.region=

# The ID of the Glue Catalog in which the metadata database resides
hive.metastore.glue.catalogid=

# Access Key and Secret Key for Glue Credentials and core-site.xml are not
# required when the MPP runs in EKS because it will use the EKS Pod Identities,
# IAM Roles for Service Accounts or the IAM EC2 instance profile, whichever is configured in EKS
hive.metastore.glue.aws-access-key=
hive.metastore.glue.aws-secret-key=
hive.config.resources=/opt/presto-server/etc/catalog/core-site.xml

hive.parquet-batch-read-optimization-enabled=true
Add feedback