[
https://issues.apache.org/jira/browse/PHOENIX-6696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6696:
---------------------------------
Release Note:
Starting with Phoenix 5.2.0, Phoenix no longer provides the legacy
phoenix-client jar.
Use the phoenix-client-embedded jar instead, and add the necessary logging
backend and corresponding slf4j adapter to the classpath separately.
was:
Starting with Phoenix 5.2.0, Phoenix no longer provides the legacy
phoenix-client jar.
Use the phoenix-client-embedded jar instead, and add necessary logging backend
and corresponding slf4j adapter to the classpath separately.
> Drop legacy phoenix-client jar
> ------------------------------
>
> Key: PHOENIX-6696
> URL: https://issues.apache.org/jira/browse/PHOENIX-6696
> Project: Phoenix
> Issue Type: Task
> Components: core
> Affects Versions: 5.2.0
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 5.2.0
>
>
> phoenix-client JAR includes log4j1 and the slf4j log4j adaptor.
> For some releases, we've been providing phoenix-client-embedded, which omits
> both the logging adaptor and backend, as well as sqlline, and is a superior
> solution that doesn't force a logging solution on the user.
> As we're switching our default logging backend to slf4j2, users of the legacy
> phoenix-client jar are likely to experience problems with the new logging
> backend anyway, this a good time to drop the legacy phoenix-client jar, and
> transitions its users to phoenix-client-embedded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
