<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.0.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>DataStax Support Forums &#187; Topic: CQL &#62;= not working as expected</title>
		<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected</link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Wed, 19 Jun 2013 09:51:17 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.0.3</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://www.datastax.com/support-forums/search.php</link>
		</textInput>
		<atom:link href="http://www.datastax.com/support-forums/rss/topic/cql-not-working-as-expected" rel="self" type="application/rss+xml" />

		<item>
			<title>jbellis on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1436</link>
			<pubDate>Tue, 27 Mar 2012 16:24:31 +0000</pubDate>
			<dc:creator>jbellis</dc:creator>
			<guid isPermaLink="false">1436@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;&#34;Secondary indexes allow for efficient querying by specific values using equality predicates (where column x = value y). Also, queries on indexed values can apply additional filters to the result set for values of other columns.&#34;&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.datastax.com/docs/1.0/ddl/indexes&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/1.0/ddl/indexes&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;More examples here: &#60;a href=&#34;http://www.datastax.com/dev/blog/whats-new-cassandra-07-secondary-indexes&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/dev/blog/whats-new-cassandra-07-secondary-indexes&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1433</link>
			<pubDate>Tue, 27 Mar 2012 14:32:13 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">1433@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I am quite new to Cassandra. I am using CQL-JDBC driver. I am not able to write query which has something.&#60;/p&#62;
&#60;p&#62;Select * From Users where age &#38;gt; 20&#60;/p&#62;
&#60;p&#62;I have created a secondary index on age. Can you please help me what is wrong ?&#60;/p&#62;
&#60;p&#62;Thanks,&#60;/p&#62;
&#60;p&#62;-Ansar
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1382</link>
			<pubDate>Fri, 16 Mar 2012 10:57:18 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">1382@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Using Astyanax (instead of Thrift or Hector) I've converted the CF to using simple row id's without the hash, and moved the hash as the first part of a composite column. Works like a charm.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1375</link>
			<pubDate>Wed, 14 Mar 2012 16:13:49 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">1375@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I think I found what is happening (see below). This means that I either use super columns (which basically are depricated) or composite columns (which are not yet supported by CQL).&#60;/p&#62;
&#60;p&#62;&#60;a href=&#34;http://www.anuff.com/2011/02/indexing-in-cassandra.html&#34; rel=&#34;nofollow&#34;&#62;http://www.anuff.com/2011/02/indexing-in-cassandra.html&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;The OrderPreservingPartitioner, as the name implies, orders the keys in string-sort order, so you can not only look up a row via a specific key, but can also traverse your set of keys in ways that are directly related to the values you are using as your keys.  In other words, if your row key was a &#34;lastname,firstname,ss#&#34; string, you could iterate through your keys in alphabetical order by lastname.  Generally, though, people try to use the RandomPartioner because, in exchange for the convenience of the OrderPreservingPartitioner, you lose the even distribution of your data across the set of nodes in your overall system, which impedes the scalability of Cassandra.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1374</link>
			<pubDate>Wed, 14 Mar 2012 16:05:09 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">1374@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I'm detecting a pattern. The rows that are found are related to the sequence in which they have been inserted. If I start with &#34;L0000001__89eb5af1fbecabc7874de697d815d4d5&#34; I find all three. If I start with &#34;L0000001__&#34; I only find the last, since it was inserted last.&#60;/p&#62;
&#60;p&#62;Should I be looking at creating indexes?
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Anonymous on "CQL &#62;= not working as expected"</title>
			<link>http://www.datastax.com/support-forums/topic/cql-not-working-as-expected#post-1373</link>
			<pubDate>Wed, 14 Mar 2012 16:00:54 +0000</pubDate>
			<dc:creator>Anonymous</dc:creator>
			<guid isPermaLink="false">1373@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I've got a simple CF which stores the result of an expression, sort of a cache, which used a prefix and a MD5 hash as the row key. At times the cache must be invalidated, so I need to scan all rows which start with the prefix, for this I wanted to use a CQL query.&#60;/p&#62;
&#60;p&#62;create column family LicenseXPath with comparator=UTF8Type and default_validation_class=UTF8Type and key_validation_class=UTF8Type;&#60;/p&#62;
&#60;p&#62;If I do a &#34;select KEY from LicenseXPath&#34; I get the following keys:&#60;br /&#62;
  L0000001__89eb5af1fbecabc7874de697d815d4d5&#60;br /&#62;
  L0000001_0027__89eb5af1fbecabc7874de697d815d4d5&#60;/p&#62;
&#60;p&#62;All keys starting with &#34;L0000001__&#34; must be invalidated. So I intended to do a &#34;select KEY from LicenseXPath where KEY &#38;gt;= 'L0000001__' and KEY &#38;lt; 'L0000001_a'&#34;, however this returns no keys. If I leave out the second condition, no rows. No matter what I do, as soon as there is a where condition I get no rows. &#60;/p&#62;
&#60;p&#62;So I manually inserted the row key &#34;L0000001__&#34;, and the select now does find that row. But only that row. &#60;/p&#62;
&#60;p&#62;I'm doing something wrong. Got some wires twisted. Question is: what wires? What am I missing?
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
