http://www.datastax.com/support-forums/tags/cql Software, Support, and Training for Apache Cassandra en-US Wed, 22 May 2013 09:56:42 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-6814 Mon, 08 Oct 2012 17:23:58 +0000 nickmbailey 6814@http://www.datastax.com/support-forums/ <p>This is actually an issue with how older versions of cql work. This is the expected behavior in CQL 2. However you shouldn't see this issue in CQL 3. Have you tried running this query in CQL 3?</p> <p>I'll also note that a row with no columns in it is the same thing as a row that does not exist. So the result you are seeing in CQL 2 can be safely interpreted as a non existent row. </p> http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-6775 Fri, 05 Oct 2012 11:40:15 +0000 jkusar 6775@http://www.datastax.com/support-forums/ <p>It looks like this bug has not been fixed. I've downloaded and installed DSE 2.2 and I still get this bug. Any chance there will be a patch soon that might fix it?</p> <p>Thanks. </p> http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-2916 Wed, 11 Jul 2012 09:41:40 +0000 Piotr Kołaczkowski 2916@http://www.datastax.com/support-forums/ <p>Yes, it will. </p> http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-2879 Tue, 10 Jul 2012 17:02:50 +0000 jkusar 2879@http://www.datastax.com/support-forums/ <p>Ok, that's great to know. Will DSE 2.2 include all of Cassandra 1.1? Specifically, will it include CQL3?</p> <p>Thanks. </p> http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-2873 Tue, 10 Jul 2012 14:55:53 +0000 Piotr Kołaczkowski 2873@http://www.datastax.com/support-forums/ <p>No, it was not on purpose, and it is definitely a bug. A series of ghost bugs have been fixed in 1.1 branch of Cassandra recently. DSE 2.1 does not include these fixes yet, but 2.2, scheduled for late July, will.</p> <p>A workaround for this would be to create additional column, and query by that column instead of the key - all columns except key should be deleted properly. </p> http://www.datastax.com/support-forums/topic/cql-selecting-by-key-always-returns#post-2868 Tue, 10 Jul 2012 11:54:27 +0000 jkusar 2868@http://www.datastax.com/support-forums/ <p>I've noticed that selecting by key in CQL always returns a record even if one doesn't actually exist:</p> <pre><code>cqlsh:pow_test&gt; select * from people; cqlsh:pow_test&gt; select * from people where key = &#039;12345&#039;; KEY ------- 12345 cqlsh:pow_test&gt; select count(*) from people; count ------- 0 cqlsh:pow_test&gt; select count(*) from people where key = &#039;12345&#039;; count ------- 1 cqlsh:pow_test&gt;</code></pre> <p>As I am currently writing a semi-generic data access layer for DSE, this makes it very difficult to detect when a row really exists or not. I don't necessarily know what columns I should check for especially given that some of them may be null and that might be completely valid.</p> <p>Was this done on purpose? Is there a way to detect via CQL whether or not a row actually exists? Ideally, will future versions of CQL only return a row if the key actually existed?</p> <p>Thanks,<br /> Jason </p> http://www.datastax.com/support-forums/topic/when-will-datastax-support-cassandra-110#post-2282 Thu, 21 Jun 2012 18:45:55 +0000 mbulman 2282@http://www.datastax.com/support-forums/ <p>We're still in the process of integrating Cassandra 1.1 into DSE. Keep an eye on the website for updates. </p> http://www.datastax.com/support-forums/topic/when-will-datastax-support-cassandra-110#post-2231 Tue, 19 Jun 2012 09:56:39 +0000 Anonymous 2231@http://www.datastax.com/support-forums/ <p>Hello together.</p> <p>Is a release date announced for Datastax Enterprise with Cassandra 1.1.0?</p> <p>Thx </p> <p>Dominik </p> http://www.datastax.com/support-forums/topic/cql-where-clause#post-2211 Mon, 18 Jun 2012 12:36:18 +0000 Anonymous 2211@http://www.datastax.com/support-forums/ <p>Xedin, thanks for the reply. I actually came across that stackoverflow post before but it doesn't help me since I need to have multiple columns compared using OR in my WHERE clause.<br /> I guess I will have to use multiple queries for now until this functionality gets added to Cassandra.</p> <p>Thanks,<br /> Erik </p> http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2169 Thu, 14 Jun 2012 08:18:01 +0000 Anonymous 2169@http://www.datastax.com/support-forums/ <p>Thanks every one for the reply!<br /> And, Thepaul, Exactly that is the place where I got the answer,<br /> If, you want to use CQL 3.0 using JDBC driver, while creating connection you have to add a few words,<br /> connection = DriverManager.getConnection("jdbc:cassandra://localhost:9160/trial?version=3.0.0");</p> <p>I mean, you have to specify the version name there.</p> <p>Thanks every one again!! </p> http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2155 Wed, 13 Jun 2012 15:38:34 +0000 thepaul 2155@http://www.datastax.com/support-forums/ <p>I wouldn't say cql 3 is still experimental. It's not even beta anymore. It ought to be as stable, or more, than cql 2 at this point.</p> <p>Version 1.1.0 of the JDBC driver (still in development) will support cql 3: see <a href="http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?spec=svn611a4f8def98d231d5aa80468c1e729a91f9259f&#038;name=trunk&#038;r=34afe6507c945ecc17fe0c2db68c1715f83af0f0" rel="nofollow">http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/source/detail?spec=svn611a4f8def98d231d5aa80468c1e729a91f9259f&#038;name=trunk&#038;r=34afe6507c945ecc17fe0c2db68c1715f83af0f0</a> .</p> <p>So if you really need it, try the v1.1.0 branch of cassandra-jdbc.</p> <p>The python driver supports cql 3 now, if that helps. </p> http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2138 Wed, 13 Jun 2012 10:20:17 +0000 Anonymous 2138@http://www.datastax.com/support-forums/ <p>I don't believe that you can do that in current situation when CQL3 is still being experimental, the only way I know to run cql3 is to run cqlsh from C* bin directory with --cql3 flag. </p> http://www.datastax.com/support-forums/topic/flexible-schema-in-cql-3#post-2131 Wed, 13 Jun 2012 03:45:48 +0000 Anonymous 2131@http://www.datastax.com/support-forums/ <p>I am new to cassandra. As, I read many posts, most of them prescribe CQL 3.0. As I am a Java developer, I was trying cassandra using JDBC driver and Hector( using cql queries) to connect to database. But, I don't know how to upgrade those to CQL 3, and CQL 3 queries are not accepted by these frameworks. So, can somebody help me out of it with some examples. </p> http://www.datastax.com/support-forums/topic/cql-where-clause#post-2129 Tue, 12 Jun 2012 20:41:24 +0000 Anonymous 2129@http://www.datastax.com/support-forums/ <p>Take a look at this <a href="http://stackoverflow.com/questions/10139390/alternative-for-or-condition-after-where-clause-in-select-statement-cassandra" rel="nofollow">http://stackoverflow.com/questions/10139390/alternative-for-or-condition-after-where-clause-in-select-statement-cassandra</a></p> <p>Short answer is - disjunctions are not currently supported in Cassandra and wouldn't be supported until probably 1.2 or later this is related to internal data organization. </p> http://www.datastax.com/support-forums/topic/cql-where-clause#post-2128 Tue, 12 Jun 2012 20:36:24 +0000 Anonymous 2128@http://www.datastax.com/support-forums/ <p>Hi, I'm new to Cassandra. I am wondering why CQL only supports using 'and' but does not support the use of 'or' in the where clause. Am I missing something about Cassandra? Do people not need to do this typically when using Cassandra?<br /> Is it recommended to just issue multiple CQL select statements, one for each column you want to filter on?</p> <p>Thanks,<br /> Erik </p>