Great. Thanks Aaron. FWIW, I am/was porting Virgil over CQL.
I should be able to release a new REST API for C* (using CQL) shortly. -brian --- Brian O'Neill Chief Architect Health Market Science The Science of Better Results 2700 Horizon Drive • King of Prussia, PA • 19406 M: 215.588.6024 • @boneill42 • healthmarketscience.com This information transmitted in this email message is for the intended recipient only and may contain confidential and/or privileged material. If you received this email in error and are not the intended recipient, or the person responsible to deliver it to the intended recipient, please contact the sender at the email above and delete this email and any attachments and destroy any copies thereof. Any review, retransmission, dissemination, copying or other use of, or taking any action in reliance upon, this information by persons or entities other than the intended recipient is strictly prohibited. On Dec 10, 2013, at 1:51 PM, Aaron Morton <aa...@thelastpickle.com> wrote: > Looks like a bug, will try to fix today > https://issues.apache.org/jira/browse/CASSANDRA-6472 > > Cheers > > ----------------- > Aaron Morton > New Zealand > @aaronmorton > > Co-Founder & Principal Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com > > On 6/12/2013, at 10:25 am, Brian O'Neill <b...@alumni.brown.edu> wrote: > >> >> I removed the data directory just to make sure I had a clean environment. >> (eliminating the possibility of corrupt keyspaces/files causing problems) >> >> -brian >> >> --- >> Brian O'Neill >> Chief Architect >> Health Market Science >> The Science of Better Results >> 2700 Horizon Drive • King of Prussia, PA • 19406 >> M: 215.588.6024 • @boneill42 • >> healthmarketscience.com >> >> This information transmitted in this email message is for the intended >> recipient only and may contain confidential and/or privileged material. If >> you received this email in error and are not the intended recipient, or the >> person responsible to deliver it to the intended recipient, please contact >> the sender at the email above and delete this email and any attachments and >> destroy any copies thereof. Any review, retransmission, dissemination, >> copying or other use of, or taking any action in reliance upon, this >> information by persons or entities other than the intended recipient is >> strictly prohibited. >> >> >> >> From: Jason Wee <peich...@gmail.com> >> Reply-To: <user@cassandra.apache.org> >> Date: Thursday, December 5, 2013 at 4:03 PM >> To: <user@cassandra.apache.org> >> Subject: Re: Drop keyspace via CQL hanging on master/trunk. >> >> Hey Brian, just out of curiosity, why would you remove cassandra data >> directory entirely? >> >> /Jason >> >> >> On Fri, Dec 6, 2013 at 2:38 AM, Brian O'Neill <b...@alumni.brown.edu> wrote: >>> When running Cassandra from trunk/master, I see a drop keyspace command >>> hang at the CQL prompt. >>> >>> To reproduce: >>> 1) Removed my cassandra data directory entirely >>> 2) Fired up cqlsh, and executed the following CQL commands in succession: >>> >>> bone@zen:~/git/boneill42/cassandra-> bin/cqlsh >>> Connected to Test Cluster at localhost:9160. >>> [cqlsh 4.1.0 | Cassandra 2.1-SNAPSHOT | CQL spec 3.1.1 | Thrift protocol >>> 19.38.0] >>> Use HELP for help. >>> cqlsh> describe keyspaces; >>> >>> system system_traces >>> >>> cqlsh> create keyspace test_keyspace with replication =3D {'class':'SimpleS= >>> trategy', 'replication_factor':'1'}; >>> cqlsh> describe keyspaces; >>> >>> system test_keyspace system_traces >>> >>> cqlsh> drop keyspace test_keyspace; >>> >>> <THIS HANGS INDEFINITELY> >>> >>> thoughts? user error? worth filing an issue? >>> One other note — this happens using the CQL java driver as well. >>> >>> -brian >>> >>> --- >>> Brian O'Neill >>> Chief Architect >>> Health Market Science >>> The Science of Better Results >>> 2700 Horizon Drive • King of Prussia, PA • 19406 >>> M: 215.588.6024 • @boneill42 • >>> healthmarketscience.com >>> >>> This information transmitted in this email message is for the intended >>> recipient only and may contain confidential and/or privileged material. If >>> you received this email in error and are not the intended recipient, or the >>> person responsible to deliver it to the intended recipient, please contact >>> the sender at the email above and delete this email and any attachments and >>> destroy any copies thereof. Any review, retransmission, dissemination, >>> copying or other use of, or taking any action in reliance upon, this >>> information by persons or entities other than the intended recipient is >>> strictly prohibited. >>> >>> >> >
