cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Adamson (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10717) Changes from CASSANDRA-9353 makes Hadoop integration backward incompatible
Date Tue, 17 Nov 2015 09:17:10 GMT


Mike Adamson commented on CASSANDRA-10717:

[~jlewandowski] Wouldn't it make more sense to have the check for the authProvider first and
then the username & password? Something like this:
if (authProvider.isPresent())
else if (username.isPresent() && password.isPresent())
    builder.withCredentials(username.get(), password.get());
This would allow for a user setting the username and password along with a non-standard auth

> Changes from CASSANDRA-9353 makes Hadoop integration backward incompatible
> --------------------------------------------------------------------------
>                 Key: CASSANDRA-10717
>                 URL:
>             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

View raw message