[PHOENIX-5772] Streamline the kerberos logic in thin client java code

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: queryserver-6.0.0
• Component/s: queryserver

Release Note

The java thin client library has been refactored. It no longer includes Hadoop libraries, and uses the Java SE Kerberos implementation directly.

The sqlline library has also been removed from the thin client JAR.

The standalone sqlline JAR is now included in the lib/ directory, and is now added to the classpath by the sqlline-thin.py script.

Some default parameters that were picked up from hbase-site.xml by the java thin client are now also handled by sqlline-thin.py

• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 12/Mar/20 06:02
• Updated: 03/Aug/21 08:35
• Resolved: 06/Apr/20 06:23

Description

The thin client has logic for sqlline-thin that automatically enablies SPNEGO based on hbase and hadoop settings and whether or not the user is is logged into kerberos.

According to my analysis, this is the only feature that this code provides. 

When using the JAR as a JDBC driver, the kerberos code does not apply.

However, this feature depends on hadoop, which carries the heavy cost bloating the thin client size and polluting its classpath.

I propose removing the the feature from the Java code, and potentially implementing it in the sqlline-thin startup script.

This would cut the JAR size by ~80%, and solve a lot of classpath problems for the users of the JDBC driver.

This is based on discussion with elserj during the review of PHOENIX-5761

Issue Links

• contains: PHOENIX-5759 Reduce thin client JAR size / classpath noise
• is related to: PHOENIX-5761 sqlline-thin kerberos logic too aggressive
• is related to: PHOENIX-4112 Allow JDBC url-based Kerberos credentials via sqlline-thin.py
• relates to: PHOENIX-5446 Support Protobuf shaded clients (thin + thick)
• links to: GitHub Pull Request #20