cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacek Lewandowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10717) Changes from CASSANDRA-9353 makes Hadoop integration backward incompatible
Date Thu, 19 Nov 2015 20:19:10 GMT

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

Jacek Lewandowski commented on CASSANDRA-10717:
-----------------------------------------------

[~mikea] Updated 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)

Mime
View raw message