Zoomdata Version

Managing the Apache Phoenix Connector

The Zoomdata Apache Phoenix connector lets you access the data available in your Apache Phoenix storage for visualization and exploration using the Zoomdata client. The Zoomdata Apache Phoenix connector supports Apache Phoenix version 4.7 and Apache Phoenix Query Server 4.7. Apache Phoenix v4.5 requires a separate download. To obtain a connector for Apache Phoenix 4.4, contact Technical Support.

Before you can establish a connection from Zoomdata to Apache Phoenix, a Zoomdata connector server for it needs to be installed, configured and enabled. See Managing Connectors for general instructions and Connecting to Apache Phoenix for details specific to the Apache Phoenix and Apache Phoenix Query Server connectors.

After the connector has been set up, you can create data source configurations that specify the necessary connection information and identify the data you want to use. See Managing Data Source Configurations for more information. After data sources are configured, they can be used to create dashboards and charts from your data. See Creating Dashboards and Creating Charts.

Zoomdata Feature Support

The Apache Phoenix and Apache Phoenix Query Server connectors support all Zoomdata features, except for the following features:

  • Box plots
  • Last value
  • Partitions
  • User delegation

Only Apache Phoenix supports Kerberos, but Apache Phoenix Query Server does not.

Apache Phoenix and Apache Phoenix Query Server support row-level expressions (derived fields) with the following limitations:

Connecting to Apache Phoenix

For Apache Phoenix, specify the JDBC URL in the following format:

jdbc:phoenix:<zk_quorum>:<zk_port>:<zk_hbase_path>

where:

  • <zk_quorum> is a comma separated list of the ZooKeeper servers
  • <zk_port> is the ZooKeeper port
  • <zk_hbase_path> is the path used by HBase to stop information about the instance

For Apache Phoenix Query Server, specify the JDBC URL in the following format:

jdbc:phoenix:thin:url=<scheme>://<server-hostname>:<port>

where:

  • <scheme> is a transport protocol for communication with the server
  • <server-hostname> is the name of the host offering the service
  • <port> is the port number on which the host is listening

Was this topic helpful?