Manage the Apache Phoenix Connector
This applies to: Visual Data Discovery
The Symphony Apache Phoenix connector lets you access the data available in your Apache Phoenix storage using the Symphony client. The Symphony 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 Symphony to Apache Phoenix, a Symphony 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 Manage Visual Data Discovery Data Sources for more information. After data sources are configured, they can be used to create dashboards and visuals from your data. See Create Dashboards.
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 | ||
---|---|---|---|---|
Y |
|
|||
N |
|
|||
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 |
|||
Y |
Apache Phoenix and Apache Phoenix Query Server connectors support row-level expressions (derived fields) with the following limitations:
|
|||
Y |
|
|||
N/A |
|
|||
Y |
|
|||
Y |
|
|||
Y |
|
|||
Y |
|
|||
Y |
|
|||
Y /N |
Apache Phoenix supports Kerberos, but Apache Phoenix Query Server does not. For more information, see Enable Kerberos Authentication for Apache Phoenix Connectors. |
|||
N |
|
|||
Y |
|
|||
N/A |
|
|||
N/A |
|
|||
N/A |
|
|||
N |
|
|||
Y |
|
|||
N/A |
|
|||
Y |
|
|||
N |
|
|||
Y |
|
|||
Y |
|
|||
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
Comments
0 comments
Please sign in to leave a comment.