Phoenix Storage Handler for Apache Hive

The Apache Phoenix Storage Handler is a plugin that enables Apache Hive access to Phoenix tables from the Apache Hive command line using HiveQL.

Prerequisites

• Phoenix 4.8.0+
• Hive 1.2.1+

Hive Setup

Make phoenix-version-hive.jar available for Hive:

Step 1: Add to hive-env.sh:

HIVE_AUX_JARS_PATH=<path to jar>

Step 2: Add a property to hive-site.xml so that Hive MapReduce jobs can use the .jar:

<property>
  <name>hive.aux.jars.path</name>
  <value>file://<path></value>
</property>

Table Creation and Deletion

The Phoenix Storage Handler supports both INTERNAL and EXTERNAL Hive tables.

Create INTERNAL Table

For INTERNAL tables, Hive manages the lifecycle of the table and data. When a Hive table is created, a corresponding Phoenix table is also created. Once the Hive table is dropped, the Phoenix table is also deleted.

    create table phoenix_table (
      s1 string,
      i1 int,
      f1 float,
      d1 double
    )
    STORED BY 'org.apache.phoenix.hive.PhoenixStorageHandler'
    TBLPROPERTIES (
      "phoenix.table.name" = "phoenix_table",
      "phoenix.zookeeper.quorum" = "localhost",
      "phoenix.zookeeper.znode.parent" = "/hbase",
      "phoenix.zookeeper.client.port" = "2181",
      "phoenix.rowkeys" = "s1, i1",
      "phoenix.column.mapping" = "s1:s1, i1:i1, f1:f1, d1:d1",
      "phoenix.table.options" = "SALT_BUCKETS=10, DATA_BLOCK_ENCODING='DIFF'"
    );

Create EXTERNAL Table

For EXTERNAL tables, Hive works with an existing Phoenix table and manages only Hive metadata. Dropping an EXTERNAL table from Hive deletes only Hive metadata but does not delete the Phoenix table.

create external table ext_table (
  i1 int,
  s1 string,
  f1 float,
  d1 decimal
)
STORED BY 'org.apache.phoenix.hive.PhoenixStorageHandler'
TBLPROPERTIES (
  "phoenix.table.name" = "ext_table",
  "phoenix.zookeeper.quorum" = "localhost",
  "phoenix.zookeeper.znode.parent" = "/hbase",
  "phoenix.zookeeper.client.port" = "2181",
  "phoenix.rowkeys" = "i1",
  "phoenix.column.mapping" = "i1:i1, s1:s1, f1:f1, d1:d1"
);

Properties

• phoenix.table.name
  • Specifies the Phoenix table name
  • Default: the same as the Hive table
• phoenix.zookeeper.quorum
  • Specifies the ZooKeeper quorum for HBase
  • Default: localhost
• phoenix.zookeeper.znode.parent
  • Specifies the ZooKeeper parent node for HBase
  • Default: /hbase
• phoenix.zookeeper.client.port
  • Specifies the ZooKeeper port
  • Default: 2181
• phoenix.rowkeys
  • The list of columns to be the primary key in a Phoenix table
  • Required
• phoenix.column.mapping
  • Mappings between column names for Hive and Phoenix. See Limitations for details.

Data Ingestion, Deletions, and Updates

Data ingestion can be done by all ways that Hive and Phoenix support:

Hive:

     insert into table T values (....);
     insert into table T select c1,c2,c3 from source_table;

Phoenix:

     upsert into table T values (.....);
         Phoenix CSV BulkLoad tools

All delete and update operations should be performed on the Phoenix side. See Limitations for more details.

Additional Configuration Options

Those options can be set in a Hive command-line interface (CLI) environment.

Performance Tuning

Query Data

You can use HiveQL for querying data in a Phoenix table. A Hive query on a single table can be as fast as running the query in the Phoenix CLI with the following property settings: hive.fetch.task.conversion=more and hive.exec.parallel=true

Limitations

• Hive update and delete operations require transaction manager support on both Hive and Phoenix sides. Related Hive and Phoenix JIRAs are listed in the Resources section.
• Column mapping does not work correctly with mapping row key columns.
• MapReduce and Tez jobs always have a single reducer.

Resources

• PHOENIX-2743 : Implementation, accepted by Apache Phoenix community. Original pull request contains modification for Hive classes.
• PHOENIX-331 : An outdated implementation with support of Hive 0.98.

原文: http://phoenix.apache.org/hive_storage_handler.html