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

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

GitHub user DT-Priyanka opened a pull request:

    https://github.com/apache/incubator-apex-malhar/pull/188

    APEXMALHAR-1948: CassandraStore Should Allow You To Specify Protocol 
Version.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/DT-Priyanka/incubator-apex-malhar 
APEXMALHAR-1948-cassandra-protocolVersion

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-apex-malhar/pull/188.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #188
    
----
commit 7bba66537db9f642a33b7422d553424bd7e3796d
Author: Priyanka Gugale <[email protected]>
Date:   2016-02-10T09:44:08Z

    APEXMALHAR-1948: CassandraStore Should Allow You To Specify Protocol 
Version.

commit 51f2720baba7671c61b559b62e7cdcf9f95ae769
Author: Priyanka Gugale <[email protected]>
Date:   2016-02-10T11:28:43Z

    Updating Cassandra driver version to 2.1.8 also adding other dependency

----


> 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)

Reply via email to