apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-1948) CassandraStore Should Allow You To Specify Protocol Version.
Date Mon, 14 Mar 2016 12:49:33 GMT

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

ASF GitHub Bot commented on APEXMALHAR-1948:
--------------------------------------------

Github user DT-Priyanka commented on a diff in the pull request:

    https://github.com/apache/incubator-apex-malhar/pull/188#discussion_r55994771
  
    --- Diff: contrib/pom.xml ---
    @@ -477,7 +477,14 @@
         <dependency>
           <groupId>com.datastax.cassandra</groupId>
           <artifactId>cassandra-driver-core</artifactId>
    -      <version>2.0.2</version>
    +      <version>2.1.8</version>
    +      <optional>true</optional>
    +    </dependency>
    +    <dependency>
    +      <groupId>com.google.guava</groupId>
    --- End diff --
    
    protocol version 3 was introduced in New in Java driver 2.1.2, that's why upgrading cassandra
driver version.


> CassandraStore Should Allow You To Specify Protocol Version.
> ------------------------------------------------------------
>
>                 Key: APEXMALHAR-1948
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-1948
>             Project: Apache Apex Malhar
>          Issue Type: Improvement
>            Reporter: Timothy Farkas
>            Assignee: Priyanka Gugale
>
> When working on an app I noticed that the default protocol version used when connecting
to cassandra was not the protocol version configured by the database. This leads to mysterious
exceptions when connecting to cassandra. The protocol should be configurable via a user property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message