Versions Compared

Old Version 39

changes.mady.by.user Lefty Leverenz

Saved on

compared with

New Version 40

changes.mady.by.user Lefty Leverenz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add links to design doc & security page for default auth

Hive Authorization

Table of Contents

Introduction

...

Three modes of Hive authorization are available to satisfy different use cases.

Use Cases

It is useful to think of authorization in terms of two primary use cases of Hive. 

  1. Hive as a table storage layer. This is the use case for Hive's HCatalog API users such as Apache Pig, MapReduce and some MPP databases. In this case, Hive provides a table abstraction and metadata for files on storage (typically HDFS). These users have direct access to HDFS and the metastore server (which provides an API for metadata access). HDFS access is authorized through the use of HDFS permissions. Metadata access needs to be authorized using Hive configuration.
  2. Hive as a SQL query engine. This is one of the most common use cases of Hive. This is the 'Hive view' of SQL users and BI tools. This use case has the following two subcategories:
    1. Hive command line users. These users have direct access to HDFS and the Hive metastore, which makes this use case similar to use case 1.
    2. ODBC/JDBC and other HiveServer2 API users. These users have all data/metadata access happening through HiveServer2. They don't have direct access to HDFS or the metastore.

...