Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Enterprise Data Preparation Service
  12. Interactive Data Preparation Service
  13. Informatica Cluster Service
  14. Mass Ingestion Service
  15. Metadata Access Service
  16. Metadata Manager Service
  17. Model Repository Service
  18. PowerCenter Integration Service
  19. PowerCenter Integration Service Architecture
  20. High Availability for the PowerCenter Integration Service
  21. PowerCenter Repository Service
  22. PowerCenter Repository Management
  23. PowerExchange Listener Service
  24. PowerExchange Logger Service
  25. SAP BW Service
  26. Search Service
  27. System Services
  28. Test Data Manager Service
  29. Test Data Warehouse Service
  30. Web Services Hub
  31. Application Service Upgrade
  32. Application Service Databases
  33. Connecting to Databases from Windows
  34. Connecting to Databases from UNIX or Linux
  35. Updating the DynamicSections Parameter of a DB2 Database

Metadata Access Service Overview

Metadata Access Service Overview

The Metadata Access Service is an application service that allows the Developer tool to access Hadoop connection information to import and preview metadata.
The Metadata Access Service contains information about the Service Principal Name (SPN) and keytab information if the Hadoop cluster uses Kerberos authentication.
Use the Administrator tool or the
infacmd
command line program to create and administer the Metadata Access Service. You can create one or more Metadata Access Services on a node. You can use one Metadata Access Service to import and preview metadata from multiple Hadoop distributions. The Metadata Access Service creates a new process to connect to each Hadoop distribution. Based on your license, the Metadata Access Service can be highly available.
If your domain has only one Metadata Access Service, the Developer tool uses the same Metadata Access Service by default to fetch metadata from multiple Hadoop distributions. If your domain has more than one Metadata Access Service, you must select a default Metadata Access Service for the Developer tool to connect to the default Metadata Access Service. Dynamic mappings do not use the Metadata Access Service.
The Developer tool does not use the Metadata Access Service to access the Databricks environment.
HBase, HDFS, Hive, and MapR-DB connections use the Metadata Access Service when you import an object from a Hadoop cluster. Google Cloud Storage connection uses Metadata Access Service to import metadata from files in Google Cloud Storage. Create and configure a Metadata Access Service before you create Google Cloud Storage, HBase, HDFS, Hive, and MapR-DB connections.