Ah, I know why. CQL 3 downcases all your identifiers by default. Wouldn't have been a problem if you had created it with CQL 3, cause then the name would be "mykeyspace" and it would match what you're asking for. But since your keyspace was created with some capital letters in its name, you just need to quote the name in CQL 3:
cqlsh> use "Mykeyspace"; p On Wed, May 16, 2012 at 3:33 AM, Cyril Auburtin <[email protected]>wrote: > well yes, since I can retrieve the keyspace and all CF (not SCF, it's > normal in cql?) with cqlsh (v2), > > tic@mPC:~$ cqlsh 1xx.xx.xxx.xx 9165 > Connected to Test Cluster at 1xx.xx.xxx.xx:9165. > [cqlsh 2.2.0 | Cassandra 1.1.0 | CQL spec 2.0.0 | Thrift protocol 19.30.0] > Use HELP for help. > cqlsh> use Mykeyspace; > cqlsh:Mykeyspace> select * from Application; > cqlsh:Mykeyspace> exit; > tic@myPC:~$ cqlsh -3 1xx.xx.xxx.xx 9165 > Connected to Test Cluster at 1xx.xx.xxx.xx:9165. > [cqlsh 2.2.0 | Cassandra 1.1.0 | CQL spec 3.0.0 | Thrift protocol 19.30.0] > Use HELP for help. > cqlsh> use Mykeyspace; > Bad Request: Keyspace 'mykeyspace' does not exist > cqlsh> > > 2012/5/14 paul cannon <[email protected]> > >> This should not be the case- a keyspace is a keyspace, however created. >> I haven't been able to reproduce this; are you sure that the cassandra-cli >> and cqlsh are connecting to the same instance? Maybe you should create a >> Jira ticket. >> >> p >> >> >> On Fri, May 11, 2012 at 2:05 PM, cyril auburtin <[email protected] >> > wrote: >> >>> yes it seems so >>> >>> as long as I create (more than just create keyspace mykeyspace) it with >>> cassandra cli, by creating CF, then I can't connect to it with cqlsh -3 >>> >>> I'll need to translate it in cql3 then >>> >>> 2012/5/11 Jason Wellonen <[email protected]> >>> >>>> ** >>>> I think you need to create the keyspace under the context of a v3 >>>> connection. Maybe someone else can confirm? >>>> >>>> >>>> ------------------------------ >>>> *From:* cyril auburtin [mailto:[email protected]] >>>> *Sent:* Friday, May 11, 2012 11:46 AM >>>> *To:* [email protected] >>>> *Subject:* Re: C 1.1 & CQL 2.0 or 3.0? >>>> >>>> thx just: can't connect to keyspace with cql 3.0 >>>> >>>> tic@my:~$ cqlsh >>>> Connected to My Cluster at 127.0.0.1:4201. >>>> [cqlsh 2.2.0 | Cassandra 1.1.0 | CQL spec 2.0.0 | Thrift protocol >>>> 19.30.0] >>>> Use HELP for help. >>>> cqlsh> use mykeyspace; >>>> cqlsh:mykeyspace> exit; >>>> tic@my:~$ cqlsh -3 >>>> Connected to My Cluster at 127.0.0.1:4201. >>>> [cqlsh 2.2.0 | Cassandra 1.1.0 | CQL spec 3.0.0 | Thrift protocol >>>> 19.30.0] >>>> Use HELP for help. >>>> cqlsh> use mykeyspace; >>>> Bad Request: Keyspace 'mykeyspace' does not exist >>>> cqlsh> >>>> >>>> ?? >>>> 2012/5/11 Jason Wellonen <[email protected]> >>>> >>>>> ** >>>>> Version 2 is the default for your connection. >>>>> >>>>> Are you using cqlsh? If so, use the "-3" parameter for version 3... >>>>> >>>>> >>>>> ------------------------------ >>>>> *From:* cyril auburtin [mailto:[email protected]] >>>>> *Sent:* Friday, May 11, 2012 10:51 AM >>>>> *To:* [email protected] >>>>> *Subject:* C 1.1 & CQL 2.0 or 3.0? >>>>> >>>>> I have C* 1.1 but it seems to only come with cql 2.0 >>>>> INFO 19:35:21,579 Cassandra version: 1.1.0 >>>>> INFO 19:35:21,581 Thrift API version: 19.30.0 >>>>> INFO 19:35:21,583 CQL supported versions: 2.0.0,3.0.0-beta1 (default: >>>>> 2.0.0) >>>>> >>>>> the problem is I would like to create such CF : >>>>> >>>>> CREATE COLUMNFAMILY TaggedPosts ( >>>>> ... tag text, >>>>> ... post uuid, >>>>> ... blog_rowentries_rowkey text, >>>>> ... PRIMARY KEY (tag, post) >>>>> ... ) WITH COMPACT STORAGE; >>>>> >>>>> and for me, (cql 2.0) it returns this error >>>>> >>>>> Bad Request: line 6:0 mismatched input ')' expecting EOF >>>>> >>>>> Is it due to the cql version? how to upgrade to 3.0, since I already >>>>> have the lastest cassandra release? >>>>> >>>> >>>> >>> >> >
