ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zsombor Gegesy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (RANGER-2135) BaseClient forces Hadoop login
Date Sun, 17 Jun 2018 19:25:00 GMT

    [ https://issues.apache.org/jira/browse/RANGER-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515200#comment-16515200
] 

Zsombor Gegesy commented on RANGER-2135:
----------------------------------------

Implementing a BaseClient subclass is not required for having a service plugin, it's just
a convention, which currently all the connector implementation follows. If you don't need
kerberos for accessing your service, then you can safely create your own CephClient, which
doesn't extends BaseClient. 
 Maybe moving the current login code into a 'BaseHadoopClient' child class from BaseClient,
and changing the parent class in every connector's  Client class would be a good idea. What
do you think? Do you want to contribute a patch for it?

> BaseClient forces Hadoop login
> ------------------------------
>
>                 Key: RANGER-2135
>                 URL: https://issues.apache.org/jira/browse/RANGER-2135
>             Project: Ranger
>          Issue Type: Bug
>          Components: plugins
>    Affects Versions: 1.0.0
>            Reporter: Bolke de Bruin
>            Priority: Major
>
> BaseClient does a login on instantiation that is bound to Hadoop. This requires service
plugins to require a username/password, which is undocumented. It also limits the functionality
to the Hadoop ecosystem.
> Suggestion:
>  * Provide a default constructor
>  * Make init() protected
>  * Make serviceName protected
>  * Make defaultConfigFile protected
> Note: I encountered this when writing a S3/Ceph plugin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message