Return-Path: X-Original-To: apmail-apex-dev-archive@minotaur.apache.org Delivered-To: apmail-apex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E5FEA1859C for ; Wed, 10 Feb 2016 11:30:24 +0000 (UTC) Received: (qmail 33788 invoked by uid 500); 10 Feb 2016 11:30:19 -0000 Delivered-To: apmail-apex-dev-archive@apex.apache.org Received: (qmail 33723 invoked by uid 500); 10 Feb 2016 11:30:19 -0000 Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.incubator.apache.org Delivered-To: mailing list dev@apex.incubator.apache.org Received: (qmail 33712 invoked by uid 99); 10 Feb 2016 11:30:19 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2016 11:30:19 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 45B0AC0E34 for ; Wed, 10 Feb 2016 11:30:19 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.462 X-Spam-Level: X-Spam-Status: No, score=-3.462 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.242] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id mSRz4mLa9WCh for ; Wed, 10 Feb 2016 11:30:18 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 842D120549 for ; Wed, 10 Feb 2016 11:30:18 +0000 (UTC) Received: (qmail 33575 invoked by uid 99); 10 Feb 2016 11:30:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2016 11:30:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 3B8302C0AFA for ; Wed, 10 Feb 2016 11:30:18 +0000 (UTC) Date: Wed, 10 Feb 2016 11:30:18 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: dev@apex.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (APEXMALHAR-1948) CassandraStore Should Allow You To Specify Protocol Version. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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 Date: 2016-02-10T09:44:08Z APEXMALHAR-1948: CassandraStore Should Allow You To Specify Protocol Version. commit 51f2720baba7671c61b559b62e7cdcf9f95ae769 Author: Priyanka Gugale 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)