Thanks, I understand better.
> What I am proposing is keeping phoenix-client-embedded, but dropping the
legacy (non embedded) phoenix-client jar/artifact from 5.2.
+1, for what it's worth. Embedding a logging back end is a bad idea as we
have learned. Only the facade (SLF4J) should be necessary.
On Tue, Apr 26, 2022 at 11:14 AM Istvan Toth <st...@cloudera.com.invalid>
wrote:
> Andrew, what you describe is the phoenix-client-embedded jar, and it is the
> (or at least my) preferred way to consume the phoenix thick client.
>
> However, we still build and publish the legacy phoenix-client (non
> embedded) JAR, that DOES include the slf4j + logging backend libraries (as
> well as sqlline + jline)
>
> What I am proposing is keeping phoenix-client-embedded, but dropping the
> legacy (non embedded) phoenix-client jar/artifact from 5.2.
>
> sqlline.py and friends used to use the non-embedded jar, so that they get
> logging and sqlline, but I have since modified all scripts to use the
> embedded client, and add the logging backend and sqlline from /lib, so
> nothing we ship depends on the legacy phoenix-client JAR any longer.
>
> regards
> Istvan
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
