| commit | 6b12e9ef119c8c7d8e07c8ba66eecafd2c0aa095 | [log] [tgz] |
|---|---|---|
| author | Istvan Toth <stoty@apache.org> | Tue Jun 16 16:35:09 2020 +0200 |
| committer | Istvan Toth <stoty@apache.org> | Thu Jun 18 13:08:11 2020 +0200 |
| tree | 004fb67e6e9494e9cb7f38077630dec606facee4 | |
| parent | 12fe6c7c56f078427d375c7fcfd5547074745020 [diff] |
PHOENIX-5771 Make standalone queryserver assembly useful again change file layout back to be similar to the main phoenix assembly remove deprecated compatibility jar symlinks rename phoenix_utils.py to phoenix_queryserver_utils.py remove hbase example config files remove load-balancer from assembly, as there was no script to start it anyway remove load-balancer jar from queryserver classpath remove lib directory from queryserver classpath copy phoenix-client to the assembly root if built with client shade guava into querserver jar, and remove from /lib dir Closes #38
Apache Phoenix enables OLTP and operational analytics in Hadoop for low latency applications. Visit the Apache Phoenix website here. This is the repo for the Phoenix Query Server (PQS).
Copyright ©2020 Apache Software Foundation. All Rights Reserved.
The Phoenix Query Server is an JDBC over HTTP abstraction. The Phoenix Query Server proxies the standard Phoenix JDBC driver and provides a backwards-compatible wire protocol to invoke that JDBC driver. This is all done via the Apache Avatica project (sub-project of Apache Calcite).
The reference client implementation for PQS is a “thin” JDBC driver which can communicate with PQS. There are drivers in other languages which exist in varying levels of maturity including Python, Golang, and .NET.
This repository will build a tarball which is capable of running the Phoenix Query Server.
By default, this tarball does not contain a Phoenix client jar as it is meant to be agnostic of Phoenix version (one PQS release can be used against any Phoenix version). Today, PQS builds against the Phoenix 4.15.0-HBase-1.4 release.
$ mvn package
To build a release of PQS which packages a specific version of Phoenix, enable the package-phoenix-client profile and specify properties to indicate a specific Phoenix version.
By default, PQS will package the same version of Phoenix used for build/test. This version is controlled by the system property phoenix.version system property. Depending on the version of Phoenix, you may also be required to use the phoenix.hbase.classifier system property to identify the correct version of Phoenix built against the version of HBase of your choosing.
$ mvn package -Dpackage.phoenix.client -Dphoenix.version=5.1.0-SNAPSHOT -Dphoenix.hbase.classifier=hbase-2.2