DEP Component Installation during Fabric Creation

Describes the Data Fabric Ecosystem Pack(DEP) component selection and installation while creating a fabric.

The following auto-provisioning templates are available during fabric creation, if you wish to install DEP components related to your use of the relevant DEP components with Data Fabric.

When you select any of the templates, except custom services, you are presented with an automatic selection of the DEP components to install. The selected set of DEP components are installed when you create the fabric.

See Ecosystem Components for information on individual DEP components.

You can select custom services to select a customized set of DEP components to install, if none of the available auto-provisioning templates for DEP fits your requirement.

NOTE
If you have selected the Custom services option, and you select an DEP component, the relevant DEP components are auto-selected based on the inter-component dependencies of the selected component or components within DEP. If you deselect any of the inter-dependent DEP components, any DEP component that has been selected earlier, and can stand on its own, is not deselected. Other dependent DEP components are automatically deselected.

For certain DEP services such as mapr-hivemetastore, mapr-hue that can work with external MySQL as the backend database, the database selection option is available on the Data Fabric UI.

You can select one of the following options for Hive metastore:
  • Embedded database: Uses the default Derby server that is available with Hive metastore.
  • Shared MySQL server: A compatible version of MariaDB is auto-installed on selecting this option. You must provide the username and password when you select this option.
  • Existing MySQL server: If you have an existing compatible version of MySQL server for the Hive Metastore. You must provide the credentials when you select this option.