Manage the Apache Phoenix Connector

Describes the Apache Phoenix connector.

The Self-Service Analytics Apache Phoenix connector lets you access the data available in your Apache Phoenix storage using the Self-Service Analytics client. The Self-Service Analytics 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 Self-Service Analytics to Apache Phoenix, a Self-Service Analytics connector server for it needs to be installed, configured and enabled. See Manage Connectors and Connector Servers for general instructions and Connect to Apache Phoenix for details specific to the Apache Phoenix and Apache Phoenix Query Server connectors.

After setting up the connector, create data sources that specify the necessary connection information and identify the data you want to use. See Create and Manage Data Sources for more information.After you set up your data sources, create dashboards, self service reports, and visuals from the data in these data sources.

Feature Support

Connector support for specific features is shown in the following table.

Key: Y - Supported; N - Not Supported; N/A - not applicable

Feature	Supported?			Notes
Admin-Defined Functions	Y
Box Plots	N
Custom SQL Queries	Y			If you need to access a BigQuery partition, explicitly include an alias for the built in partition column in your select clause, such as select *, _PARTITIONTIME as pt from projectId.datasetId.tableId.
Derived Fields (Row-Level Expressions)	Y			Apache Phoenix and Apache Phoenix Query Server connectors support row-level expressions (derived fields) with the following limitations: The filter IS NULL does not work properly on grouped fields. The LOCATE text row-level function only supports a constant as a argument. A COALESCE conditional row-level function specified with and empty argument does not work properly. If the CASE conditional row-level function returns a null value as a an argument of another function, a NullPointerException may occur. The LPAD and RPAD text row-level functions are not supported.
Distinct Counts	Y
Fast Distinct Values	N/A
Group By Multiple Fields	Y
Group By Time	Y
Group By UNIX Time	Y
Histogram Floating Point Values	Y
Histograms	Y
Kerberos Authentication	Y / N			Apache Phoenix supports Kerberos, but Apache Phoenix Query Server does not. For more information, see Enable Kerberos Authentication for Apache Phoenix Connectors.
Last Value	N
Live Mode and Playback	Y
Multivalued Fields	N/A
Nested Fields	N/A
Partitions	N/A
Pushdown Joins for Fusion Data Sources	N
Schemas	Y
Text Search	N/A
TLS	Y
User Delegation	N
Wildcard Filters	Y
Wildcard Filters, Case-Insensitive Mode	Y
Wildcard Filters, Case-Sensitive Mode	Y

Connect 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 microservice
• <port> is the port number on which the host is listening

Add Patched JAR Files to an Apache Phoenix Connector’s Classpath

If your Apache Phoenix/HBase servers use patched .jar files, you might need to add the patched .jar files to the Apache Connector’s classpath. If you do not, Apache Phoenix may produce an error indicating that you have outdated .jar files.

Add the patched .jar files to the Apache Phoenix connector’s classpath:

1. Add the patched .jar files to a directory that is accessible to the connector. For example:

   /usr/local/share/java/zoomdata/phoenix
   

2. Add or modify the following property in the /etc/zoomdata/edc-phoenix-4.7.properties file to specify the path to your .jar files as a comma-separated list in loader.path property. Be sure to put the path to your .jar files first so you do not corrupt entries already present in this property. For example:

   loader.path=/usr/local/share/java/zoomdata/phoenix,lib/edc-phoenix-4.7/phoenix-core-4.7.0-HBase-1.1.jar
   

Enable Kerberos Authentication for Apache Phoenix Connectors

Support for Kerberos authentication for Self-Service Analytics Apache Phoenix connectors is only provided for Phoenix 4.7 (and later) connectors. It is not provided for any version of the Phoenix QueryServer connector.

Enable Kerberos authentication for Apache Phoenix connectors:

1. Download hbase-site.xml and core-site.xml files from the Apache HDFS and HBase microservices. For example, for Hortonworks you can use the instructions at the following link: https://docs.cloudera.com/HDPDocuments/Ambari-2.6.2.2/bk_ambari-operations/content/downloading_client_configs.html.

2. Add the following configuration options to the hbase-site.xml file:

   <property>
       <name>hbase.myclient.principal</name>
       <value>YOUR_PRINCIPAL</value>
   </property>
   <property>
       <name>hbase.myclient.keytab</name>
       <value>PATH_TO_YOUR_KEYTAB</value>
   </property>
   

   Substitute the ID of your Kerberos principal for YOUR_PRINCIPAL and the path to your Kerberos keytab file for PATH_TO_YOUR_KEYTAB.

3. Verify that the core-site.xml file contains the following entry:

   <property>
       <name>hadoop.security.authentication</name>
       <value>kerberos</value>
   </property>
   

4. Make sure that the Apache Phoenix connector has access to the hbase-site.xml and core-site.xml files as well as the Kerberos keytab file you identified in PATH_TO_YOUR_KEYTAB. We recommend that you place these files in the /etc/zoomdata/edc-phoenix directory.

5. Add the following property to the /etc/zoomdata/edc-phoenix-4.7.properties file to direct the Apache Phoenix connector to the files you created

   datasource.config.files-path=/etc/zoomdata/edc-phoenix
   
   Self-Service Analytics does not recommend that you provide the Kerberos principal ID and keytab file path using a JDBC URL. The Apache Phoenix driver has a bug that will not refresh a ticket after expiration.