Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D872C651 for ; Fri, 25 Jan 2013 12:28:01 +0000 (UTC) Received: (qmail 28520 invoked by uid 500); 25 Jan 2013 12:27:59 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 28207 invoked by uid 500); 25 Jan 2013 12:27:57 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 28176 invoked by uid 99); 25 Jan 2013 12:27:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 12:27:56 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mishra.vivs@gmail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ea0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Jan 2013 12:27:49 +0000 Received: by mail-ea0-f175.google.com with SMTP id d1so135482eab.34 for ; Fri, 25 Jan 2013 04:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=gunlTUUC/e8te7I9X3Yq2fGStGdyP+tueDOWsX3ZUD4=; b=dPgt4viLVCndiWudb03kxqrxHSB2uIOUQqGUxbot99SekhkX8+41fx+cj48q44y0IW s33Fv+dZN4Agtoh2i5hiE7apLSQrlZK/3c0Ki5OilpkKu1DW3DI/GayV/oSb2GRNwu/4 5IITpYkVF13rlJMh/mA6VLca57tcs36AUMF0P6ElpC3aCMY5VqGv2Y1K+ZsT7nUJrmM5 Jjmu2qOlNESftcmA4Vgpx2OoQtrWSoVSYOmxnP+trXeDETwKoCtqYuICtvrrKH8JjaBc ynjzKSfvZAV7EsS9I4xBye+nzITybaVKl6Btkgo/oU3ZGeq68gf0yHmt6DEs0FbpUYVQ m1Tg== MIME-Version: 1.0 X-Received: by 10.14.215.194 with SMTP id e42mr17559121eep.32.1359116849605; Fri, 25 Jan 2013 04:27:29 -0800 (PST) Received: by 10.223.18.12 with HTTP; Fri, 25 Jan 2013 04:27:29 -0800 (PST) In-Reply-To: References: Date: Fri, 25 Jan 2013 17:57:29 +0530 Message-ID: Subject: Re: Cassandra-cli : with CQL binary protocol From: Vivek Mishra To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8f923f50076cd704d41c0db4 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f923f50076cd704d41c0db4 Content-Type: text/plain; charset=ISO-8859-1 Any suggestions? Once i enable *native_transport_port: 9042*, it will not start cassandra thrift automatically, Even if *start_rpc: true* ? Or it should start listening to both ports? On Fri, Jan 25, 2013 at 4:39 PM, Vivek Mishra wrote: > Means start 2 instances , 1 for thrift based access and another for > native? Of course on different port. > > Once i enable *native_transport_port: 9042*, it will not start cassandra > thrift automatically? Even if *start_rpc: true* > > -Vivek > > > On Fri, Jan 25, 2013 at 4:33 PM, Sylvain Lebresne wrote: > >> Well, the cassandra-cli uses the thrift protocol, so it will not work is >> you use start_rpc: false. >> Whether you start the binary protocol server has no real impact as >> Cassandra is fine starting both server (as long as you don't set the same >> port for both for obvious reasons). >> Obviously, if you point cassandra-cli to the port used by the binary >> protocol, that won't work either. >> >> -- >> Sylvain >> >> >> On Fri, Jan 25, 2013 at 11:53 AM, Vivek Mishra wrote: >> >>> Is this a valid assumption that cassandra-cli will not work, if >>> Cassandra server is getting started by enabling CQL binary protocol? >>> >>> -Vivek >>> >> >> > --e89a8f923f50076cd704d41c0db4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Any suggestions?

Once i enable native_transport_port: 9042, = it will not start cassandra thrift automatically, Even if start_rpc: tru= e ? Or it should start listening to both ports?




On Fri, Jan 25, 2013 at 4:39 PM, Vivek Mishra <mishra.vivs@gmail.com> wrote:
Means start 2 instances , 1 for thrift based access and another for native?= Of course on different port.

Once i enable native_transport_port= : 9042, it will not start cassandra thrift automatically? Even if st= art_rpc: true

-Vivek


On Fri, Jan 25, 2013 at 4:33 PM, Sylvain Lebresne <= span dir=3D"ltr"><sylvain@datastax.com> wrote:
Well, the cassandra-cli uses the thrift protocol, so it wi= ll not work is you use start_rpc: false.
Whether you start the binary p= rotocol server has no real impact as Cassandra is fine starting both server= (as long as you don't set the same port for both for obvious reasons).=
Obviously, if you point cassandra-cli to the port used by the binary p= rotocol, that won't work either.

--
= Sylvain


On Fri, Jan 25, 2013 at 11:53 AM, Vivek Mish= ra <mishra.vivs@gmail.com> wrote:
Is this a valid assumption that cassandra-cli will not work, if Cassandra s= erver is getting started by enabling CQL binary protocol?

-Vivek



--e89a8f923f50076cd704d41c0db4--