You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jacek Lewandowski (JIRA)" <ji...@apache.org> on 2015/11/19 21:18:11 UTC
[jira] [Updated] (CASSANDRA-10717) Changes from CASSANDRA-9353
makes Hadoop integration backward incompatible
[ https://issues.apache.org/jira/browse/CASSANDRA-10717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacek Lewandowski updated CASSANDRA-10717:
------------------------------------------
Attachment: CqlConfigHelper_authentication_patch-2.patch
> 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-2.patch, 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)