Re: [DISCUSS] Unbundling Sqlline and slf4j backend from phoenix-client and phoenix-client embedded

2021-05-26 Thread Istvan Toth
The technical details: The plan is to ship the sqlline ubjerjar (sqlline provides an uberjar with all of its own dependencies shaded in) in the /lib directory, along with the log4j slf4j backend jar. sqlline.py and friends is to be updated to add those to the classpath. Richard has this already

Re: [DISCUSS] Unbundling Sqlline and slf4j backend from phoenix-client and phoenix-client embedded

2021-05-26 Thread Josh Elser
I think the idea is that we would include a sqlline jar with the Phoenix distribution. Context: we had some grief where a sqlline upgrade caused user pain because they were relying on specific output from sqlline. If we have the sqlline jar _not_ packaged inside phoenix-client, then users can

Re: [DISCUSS] Unbundling Sqlline and slf4j backend from phoenix-client and phoenix-client embedded

2021-05-26 Thread la...@apache.org
Will sqlline still be part of the Phoenix "distribution"? Or will it become a separate package to install? On Wednesday, May 26, 2021, 1:07:17 AM PDT, Istvan Toth wrote: Hi! The current purpose of the phoenix-client JAR is twofold: - It servers as a generic JDBC driver for

[DISCUSS] Unbundling Sqlline and slf4j backend from phoenix-client and phoenix-client embedded

2021-05-26 Thread Istvan Toth
Hi! The current purpose of the phoenix-client JAR is twofold: - It servers as a generic JDBC driver for embedding in applications - It also contains the sqlline library used by the sqlline.py script, as well as the slf4j log4j backend. - (It also contains a some Phoenix code and HBase libraries