[
https://issues.apache.org/jira/browse/PHOENIX-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6660:
---------------------------------
Release Note:
The Phoenix Query Server assembly now includes the reload4j and slf4j-reload4j
jars.
In order to avoid logging jar conflicts, Phoenix Query Server now has to be run
with the phoenix-embedded-client jar variant, instead of the non-embedded
phoenix-client jar.
sqlline-thin.py now uses reload4j and the bin/logj.properties file for logginig.
> Ship reload4j in queryserver assembly
> -------------------------------------
>
> Key: PHOENIX-6660
> URL: https://issues.apache.org/jira/browse/PHOENIX-6660
> Project: Phoenix
> Issue Type: Improvement
> Components: queryserver
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
>
> Queryserver currently doesn't ship any "real" logging backend, it only adds
> slf4j-simple.
> If you add the non embedded phoenix-client, then it will pick up the slf4j
> backend and slf4j from it, and work, but if you use phoenix-client-embedded,
> you only get the very limited slf4j-simple backend.
> Add reload4j to the assembly, and change the scripts to load those JARs.
> Also document that you should use the embedded client, and how to remove the
> bundled logging jars if you use the non-embedded client.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
