You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2020/03/12 14:15:00 UTC

[jira] [Updated] (PHOENIX-5772) Streamline the kerberos logic in thin client java code

     [ https://issues.apache.org/jira/browse/PHOENIX-5772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Istvan Toth updated PHOENIX-5772:
---------------------------------
    Summary: Streamline the kerberos logic in thin client java code  (was: Remove the kerberos logic from thin client java code)

> Streamline the kerberos logic in thin client java code
> ------------------------------------------------------
>
>                 Key: PHOENIX-5772
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5772
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)