<?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; User Favorites: khahn</title>
		<link><a href='http://www.datastax.com/support-forums/profile/khahn'>khahn</a></link>
		<description>Software, Support, and Training for Apache Cassandra</description>
		<language>en-US</language>
		<pubDate>Wed, 22 May 2013 09:35:23 +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/profile/" rel="self" type="application/rss+xml" />

		<item>
			<title>Jack Krupansky on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-10626</link>
			<pubDate>Sun, 05 May 2013 15:34:28 +0000</pubDate>
			<dc:creator>Jack Krupansky</dc:creator>
			<guid isPermaLink="false">10626@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;In general, it is best to create a &#34;Solr&#34; column family from scratch using the Solr HTTP APPI. You can then populate the column family using either the Solr or Cassandra APIs.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>rahul on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-10592</link>
			<pubDate>Sat, 04 May 2013 04:04:24 +0000</pubDate>
			<dc:creator>rahul</dc:creator>
			<guid isPermaLink="false">10592@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Here i am using DSE3.0.1. I  am creating a composite column family through cassandra-cli.But at indexing solr gives error that &#34;Solr indexes are not supported on ColumnFamilies with non-string comparators&#34;.Where am i missing? Please help me. I have badly need it. It'll be very great-full for you.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>avon on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9622</link>
			<pubDate>Sun, 31 Mar 2013 11:33:15 +0000</pubDate>
			<dc:creator>avon</dc:creator>
			<guid isPermaLink="false">9622@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Seems Solr always require a unique id to be configured under it's index designated in the schema.xml config file. A CQL3 table with a simple and single index can be easily resolved to a unique id as required by Solr - and my guess - when the index is a composite one, that's where Solr &#38;amp; DSE integration finds it unable to decide on which one to use as unique key given multiple fields in a composite index. Or perhaps should use all fields in a composite index as unique key!&#60;br /&#62;
Anyway what I hear is CQL3 and SOLR is not integrated yet...and only single field index works for now...please correct my understanding
&#60;/p&#62;</description>
		</item>
		<item>
			<title>khahn on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9618</link>
			<pubDate>Sat, 30 Mar 2013 05:14:07 +0000</pubDate>
			<dc:creator>khahn</dc:creator>
			<guid isPermaLink="false">9618@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;We added an example to the docs to show how to insert your own data for searching into Cassandra: &#60;a href=&#34;http://www.datastax.com/docs/datastax_enterprise3.0/solutions/dse_search_load_data&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/datastax_enterprise3.0/solutions/dse_search_load_data&#60;/a&#62;&#60;/p&#62;
&#60;p&#62;The example uses CQL 2. CQL 3 isn't supported yet. Hope this helps.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Jack Krupansky on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9606</link>
			<pubDate>Fri, 29 Mar 2013 18:21:54 +0000</pubDate>
			<dc:creator>Jack Krupansky</dc:creator>
			<guid isPermaLink="false">9606@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;To be clear, DSE doesn't specifically support creation of a Solr-enabled column family using CQL. But, once created using the DSE/Solr HTTP API, that column family can be queried with CQL by using the WHERE solr_query='query-string' clause.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Jack Krupansky on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9605</link>
			<pubDate>Fri, 29 Mar 2013 15:08:40 +0000</pubDate>
			<dc:creator>Jack Krupansky</dc:creator>
			<guid isPermaLink="false">9605@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;It is easier and better to completely create a Solr-enabled column family using the Solr HTTP API, as shown in the DSE doc with the Wikipedia demo. In fact, start with the solrconfig.xml for that demo, and modify the schema as well.&#60;/p&#62;
&#60;p&#62;If you do that, you will see all the detailed metadata and column family parameters that DSE/Solr automatically creates for you. Do you really want to do all of that by hand?!&#60;/p&#62;
&#60;p&#62;Meanwhile, I will research whether there technical issues with CQL3 for Solr. I mean, you should be able to create a Solr-enabled column family that way if you actually really want to.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>avon on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9600</link>
			<pubDate>Fri, 29 Mar 2013 08:43:55 +0000</pubDate>
			<dc:creator>avon</dc:creator>
			<guid isPermaLink="false">9600@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;I tried all table combinations&#60;br /&#62;
1. with all fields as varchars and compsite index - fails&#60;br /&#62;
2. with all fields different data types and single field index - is ok&#60;br /&#62;
3. all fields different data types and composite index - fails&#60;/p&#62;
&#60;p&#62;Seems table with composite index is not workable in Solr and the irony is without composite key you miss the clustering guarantees per partition akin to column family with dynamic columns...
&#60;/p&#62;</description>
		</item>
		<item>
			<title>avon on "Error creating Solr indexes on CQL3 created tables"</title>
			<link>http://www.datastax.com/support-forums/topic/error-creating-solr-indexes-on-cql3-created-tables#post-9599</link>
			<pubDate>Fri, 29 Mar 2013 05:05:03 +0000</pubDate>
			<dc:creator>avon</dc:creator>
			<guid isPermaLink="false">9599@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi,&#60;/p&#62;
&#60;p&#62;I created a table using CQL3 and subsequently went ahead to create a Solr index and encountered this error when curl-ing the solrconfig.xml. &#60;/p&#62;
&#60;p&#62;CREATE TABLE receiptrepository (&#60;br /&#62;
	CustomerId uuid,&#60;br /&#62;
	ReceiptDate timestamp,&#60;br /&#62;
	ReceiptId uuid,&#60;br /&#62;
	MerchantName varchar,&#60;br /&#62;
	MallName varchar,&#60;br /&#62;
   PRIMARY KEY (CustomerId, ReceiptDate, ReceiptId, MerchantName, MallName)&#60;br /&#62;
   );&#60;/p&#62;
&#60;p&#62;curl --data-binary file=@solrconfig.xml -H 'Content-type:text/xml; charset=utf-8' &#60;a href=&#34;http://192.168.56.135:8983/solr/resource/demodb.receiptrepository/solrconfig.xml&#34; rel=&#34;nofollow&#34;&#62;http://192.168.56.135:8983/solr/resource/demodb.receiptrepository/solrconfig.xml&#60;/a&#62;   (btw, solrconfig.xml is reused from wiki-solr demo)&#60;/p&#62;
&#60;p&#62;error I get: &#34;Solr indexes are not supported on ColumnFamilies with non-string comparators&#34; &#60;/p&#62;
&#60;p&#62;1. Could you explain what is wrong with the TABLE creation to elicit this response during solr index creation?&#60;br /&#62;
2. Also on a side note: when I executed the wiki-solr demo and launched the solr admin, I'm unable to see the full query interface and wiki-solr doesn't appear on the left menu option (below thread dump)
&#60;/p&#62;</description>
		</item>
		<item>
			<title>lc2a on "Datastax Java Driver"</title>
			<link>http://www.datastax.com/support-forums/topic/datastax-java-driver#post-9471</link>
			<pubDate>Mon, 18 Mar 2013 00:07:36 +0000</pubDate>
			<dc:creator>lc2a</dc:creator>
			<guid isPermaLink="false">9471@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi All,&#60;/p&#62;
&#60;p&#62;May I know how to run CQL3 in MapReduce.&#60;br /&#62;
CREATE TABLE payloads (&#60;br /&#62;
  pinter varchar,&#60;br /&#62;
  computer varchar,&#60;br /&#62;
  snapshot_date int,&#60;br /&#62;
  xml_data text,&#60;br /&#62;
  status varchar,&#60;br /&#62;
  PRIMARY KEY ((pinter, computer), snapshot_date)&#60;br /&#62;
)&#60;/p&#62;
&#60;p&#62;How to integrate Datastax Java Driver or Astyanax into MapReduce ColumnFamilyInputFormat class.&#60;/p&#62;
&#60;p&#62;Thanks in advance.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>mbulman on "No dsc12 package in yum repository."</title>
			<link>http://www.datastax.com/support-forums/topic/no-dsc12-package-in-yum-repository#post-8905</link>
			<pubDate>Mon, 04 Feb 2013 16:55:09 +0000</pubDate>
			<dc:creator>mbulman</dc:creator>
			<guid isPermaLink="false">8905@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Philip,&#60;/p&#62;
&#60;p&#62;The community (DSC) and enterprise (DSE) packages live in separate repositories.  You can see the instructions for installing the DSE RPM here: &#60;a href=&#34;http://www.datastax.com/docs/datastax_enterprise2.2/install/install_rpm_pkg&#34; rel=&#34;nofollow&#34;&#62;http://www.datastax.com/docs/datastax_enterprise2.2/install/install_rpm_pkg&#60;/a&#62;
&#60;/p&#62;</description>
		</item>
		<item>
			<title>philip.fielder_bhnetwork.com on "No dsc12 package in yum repository."</title>
			<link>http://www.datastax.com/support-forums/topic/no-dsc12-package-in-yum-repository#post-8890</link>
			<pubDate>Mon, 04 Feb 2013 03:18:54 +0000</pubDate>
			<dc:creator>philip.fielder_bhnetwork.com</dc:creator>
			<guid isPermaLink="false">8890@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;doesn't look like the DSE version is available either:&#60;/p&#62;
&#60;p&#62;[root@ip-10-180-105-227 ~]# yum install dse-full opscenter&#60;br /&#62;
Loaded plugins: security&#60;br /&#62;
Repository epel is listed more than once in the configuration&#60;br /&#62;
rightscale-epel                                                                                                                        &#124;  951 B     00:00&#60;br /&#62;
Excluding Packages from none&#60;br /&#62;
Finished&#60;br /&#62;
Setting up Install Process&#60;br /&#62;
No package dse-full available.&#60;br /&#62;
No package opscenter available.&#60;br /&#62;
Nothing to do&#60;br /&#62;
[end]&#60;/p&#62;
&#60;p&#62;I don't know why you document this feature on your website when it is not ready.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Janbalik on "Why a 3rd column family when creating a custom index on Cassandra?"</title>
			<link>http://www.datastax.com/support-forums/topic/why-a-3rd-column-family-when-creating-a-custom-index-on-cassandra#post-8850</link>
			<pubDate>Fri, 01 Feb 2013 17:00:12 +0000</pubDate>
			<dc:creator>Janbalik</dc:creator>
			<guid isPermaLink="false">8850@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Since I think someone else could have the same doubt than me, I'm going to answer my own question with the things I have found:&#60;/p&#62;
&#60;p&#62;As I supposed the main problem is the concurrency. If we assume that many users at the same time can be changing the same indexed value, as you have to read the index before updating, between the time you read a value and the time you update a value in the index another user could have changed again that value. As well as, from the moment the value is updated until you update the index the system could crash. Then, after a few concurrent changes the index could have old values that point to rows that have not that value. &#60;/p&#62;
&#60;p&#62;By adding the third column family this process is safer but NOT 100% SAFE. &#60;/p&#62;
&#60;p&#62;And a last thing: from my understanding, if there is no concurrency when updating the values, then there must be no problem. Let's supose you are indexing some user data. If  only the owner of the data is allowed to modify the data, there is no concurrency at all. The unique risk is the system crashes before you finish the process to align the index with the value, but this operation is idempotent, so you can repeat it until success. &#60;/p&#62;
&#60;p&#62;Hope this explain what I have understood and help others.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>Janbalik on "Why a 3rd column family when creating a custom index on Cassandra?"</title>
			<link>http://www.datastax.com/support-forums/topic/why-a-3rd-column-family-when-creating-a-custom-index-on-cassandra#post-8702</link>
			<pubDate>Sun, 27 Jan 2013 10:54:22 +0000</pubDate>
			<dc:creator>Janbalik</dc:creator>
			<guid isPermaLink="false">8702@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Hi Khahn, &#60;/p&#62;
&#60;p&#62;Don't say sorry friend ;) You are helping me! Thank you very much. I'm still tring to understand this. I think a key is this: &#34;Updates to the index an data are not atomic&#34;. Another one is &#34;a node might index data held by another node&#34;. This is aligned with what I thought: you can have an index to a data which does not exist or a data not indexed. But, why using a third with the values indexed we can avoid this problem? We could say updates to the index, data and values indexes are not atomic, I mean, from my understanding, there could be concurrency and consistency problems also between the third CF (values indexed) and data. Or am I wrong? If so, why? Can you (or anyone) explain me why I'm wrong? &#60;/p&#62;
&#60;p&#62;Thanks!!
&#60;/p&#62;</description>
		</item>
		<item>
			<title>michael.figuiere on "Datastax Java Driver"</title>
			<link>http://www.datastax.com/support-forums/topic/datastax-java-driver#post-8642</link>
			<pubDate>Thu, 24 Jan 2013 23:21:20 +0000</pubDate>
			<dc:creator>michael.figuiere</dc:creator>
			<guid isPermaLink="false">8642@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;This driver is already quite stable but is not considered production ready yet. We'll iterate through some betas and rc releases over the upcoming weeks. We'll validate it internally and we currently plan release a 1.0 GA in the second half of March 2013.&#60;/p&#62;
&#60;p&#62;If you need to go in production right now with a project then you'd probably prefer to go with one of the currently available client libraries for Java. But if the release plan that I've mentioned above fits your project schedule, then you should give it a try.
&#60;/p&#62;</description>
		</item>
		<item>
			<title>khahn on "Why a 3rd column family when creating a custom index on Cassandra?"</title>
			<link>http://www.datastax.com/support-forums/topic/why-a-3rd-column-family-when-creating-a-custom-index-on-cassandra#post-8617</link>
			<pubDate>Thu, 24 Jan 2013 02:09:59 +0000</pubDate>
			<dc:creator>khahn</dc:creator>
			<guid isPermaLink="false">8617@http://www.datastax.com/support-forums/</guid>
			<description>&#60;p&#62;Sorry the link didn't answer your question. I learned a little more after researching your question, but I'm afraid it's not a complete answer. I hope an expert gives you a better explanation soon. &#60;/p&#62;
&#60;p&#62;The third column family is needed because simply reading the previous value from the users CF before updating it and then removing the index entry for that value from the Users_Index_Entries will not reliably work due to Cassandra's model of eventual consistency and lack of transactions. When creating your own index, a node might index data held by another node. Updates to the index and data are not atomic. To overcome these problems, you maintain a third column family to list previous values for the property of an item and use the list to remove these values from the index before adding the new value to the index.
&#60;/p&#62;</description>
		</item>

	</channel>
</rss>
