[
https://issues.apache.org/jira/browse/CASSANDRA-10717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008552#comment-15008552
]
Jacek Lewandowski commented on CASSANDRA-10717:
-----------------------------------------------
[~mikea] - i'm afraid that it won't be very useful because of the following
reasons:
* the {{AuthProvider}} instance obtained few lines before, if it is
{{PlainTextAuthProvider}}, it is already initialised with username and
password, so the credentials are set in this case
* {{withCredentials}} method implicitly set the auth provider to be
{{PlainTextAuthProvider}}, so if there is already some other auth provider set,
it will be overridden by {{PlainTextAuthProvider}}; that method doesn't set
credentials in a generic way on the currently selected authenticator
> Changes from CASSANDRA-9353 makes Hadoop integration backward incompatible
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-10717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10717
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jacek Lewandowski
> Assignee: Jacek Lewandowski
> Attachments: CqlConfigHelper_authentication_patch.patch
>
>
> Previously {{CqlInputFormat.getSplits(JobContext)}} method did not require
> anything but providing username and password in order to work with password
> protected Cassandra. Now, since CASSANDRA-9353 moved this part of the code
> from Thrift to Java Driver, the user needs to explicitly select
> {{AuthProvider}} to make it work.
> I propose a simple change in {{CqlConfigHelper}} which make
> {{CqlConfigHelper.getCluster}} method set credentials on {{Cluster.Builder}}
> if they are present in the configuration, prior to setting {{AuthProvider}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
