Table of Contents

Search

  1. Preface
  2. Introduction to Data Engineering Administration
  3. Authentication
  4. Running Mappings on a Cluster with Kerberos Authentication
  5. Authorization
  6. Cluster Configuration
  7. Cloud Provisioning Configuration
  8. Data Integration Service Processing
  9. Appendix A: Connections Reference
  10. Appendix B: Monitoring REST API

SQL Authorization for Hive

SQL Authorization for Hive

SQL standards-based authorization enables database administrators to impose fine grained authorization on Hive tables and views when you read data from a Hive source or a target.
Informatica supports fine grained authorization for Hive sources with Blaze engine, and Hive sources and targets with Spark engines. You can use the Ranger authorization plug-in when you enable fine grained authorization for mappings that run on a Hortonworks HDP cluster.
You can use the Sentry authorization plug-in when you enable fine grained authorization for mappings that run on a Cloudera cluster. When the mapping accesses Hive sources in Blaze engine and Hive sources and targets in Spark engine on a cluster that uses Sentry authorization and runs in native mode, you can use SQL authorization on the column level if you configure hive.server2.proxy.user in the Hive JDBC connect string.
In this case, the mapping uses the hive.server2.proxy.user value to access Hive sources and targets. When you also configure the mappingImpersonationUserName property, then the mapping uses the mappingImpersonationUserName value to access Hive sources and targets.
You can configure a Hive connection to observe fine grained authorization.

0 COMMENTS

We’d like to hear from you!