DataStax Support Forums » User Favorites: fadi

DataStax Support Forums » User Favorites: fadi fadi Software, Support, and Training for Apache Cassandra en-US Tue, 21 May 2013 10:42:18 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php Jack Krupansky on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8558 Mon, 21 Jan 2013 18:56:25 +0000 Jack Krupansky 8558@http://www.datastax.com/support-forums/ For now, stick with Solr "string" and CQL "text"/UTF8Type for the primary/unique key type. Fadi on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8551 Mon, 21 Jan 2013 10:29:43 +0000 Fadi 8551@http://www.datastax.com/support-forums/ What is the conclusion of this? If Cassandras table is using UUID type ID, then I cant use it as a unique id in SOLR? Solr is able to assign/generate UUIDs, but when tested on DSE 2.2.1 we get java.lang.RuntimeException: org.apache.solr.common.SolrException: Error loading class 'solr.UUIDUpdateProcessorFactory' The class exists in solr core jar file from apache but not the one bundled in DSE, is it OK to replace DSE solr jar files with ones ( same version ) from the net? Regards /Fadi tristanls on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8430 Tue, 15 Jan 2013 17:12:19 +0000 tristanls 8430@http://www.datastax.com/support-forums/ Success! Thank you. The response if everything goes well is something like (as opposed to <code>SUCCESS</code>): <code> <?xml version="1.0" encoding="UTF-8"?> <response> <lst name="responseHeader"><int name="status">0</int><int name="QTime">52</int></lst> </response> </code> Both of your corrections were necessary (remove "/resource" and square brackets). I was surprised that square brackets were necessary, as the example from <a href="http://wiki.apache.org/solr/UpdateJSON" rel="nofollow">http://wiki.apache.org/solr/UpdateJSON</a> for Solr 4.0 (at the bottom) shows posting without square brackets: <code> curl <a href="http://localhost:8983/solr/update" rel="nofollow">http://localhost:8983/solr/update</a> -H 'Content-type:application/json' -d ' { "id" : "TestDoc1", "title" : {"set":"test1"}, "revision" : {"inc":3}, "publisher" : {"add":"TestPublisher"} }' </code> Thanks again, Cheers Jack Krupansky on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8429 Tue, 15 Jan 2013 17:00:31 +0000 Jack Krupansky 8429@http://www.datastax.com/support-forums/ Sorry for not noticing this before... take "/resource" out of your URLs. Too bad DSE is not giving you a proper error response. Also, you need square brackets around the document list, which is a JSON array of documents. For example: curl <a href="http://localhost:8983/solr/initialtiny.solr/update/json?commit=true" rel="nofollow">http://localhost:8983/solr/initialtiny.solr/update/json?commit=true</a> -H 'Content-Type:application/json' -d '[{"id":"aecfd710-5b64-11e2-bcfd-0800205c9a67","body":"This is my awesome text. I hope it gets indexed"}]' -v tristanls on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8425 Tue, 15 Jan 2013 15:04:35 +0000 tristanls 8425@http://www.datastax.com/support-forums/ I changed <code>schema.xml</code> to: <code> <schema name="initialtiny" version="1.1"> <types> <fieldType name="string" class="solr.StrField"/> <fieldType name="text" class="solr.TextField"> <analyzer> <tokenizer class="solr.StandardTokenizerFactory"/> </analyzer> </fieldType> </types> <fields> <field name="id" type="string" indexed="true" stored="true"/> <field name="body" type="text" indexed="true" stored="true"/> </fields> <defaultSearchField>body</defaultSearchField> <uniqueKey>id</uniqueKey> </schema> </code> No change in behavior. (no data in Cassandra, no responses for <code>*:*</code> query, <code>Column Name: _solr_update/json</code> with document contents as <code>Index Options</code> gets created instead) Jack Krupansky on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8413 Tue, 15 Jan 2013 00:33:39 +0000 Jack Krupansky 8413@http://www.datastax.com/support-forums/ Sorry for the confusion. The field type for your "id" field should be "string", not UUID. tristanls on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8412 Mon, 14 Jan 2013 19:27:09 +0000 tristanls 8412@http://www.datastax.com/support-forums/ Just tried it with the <code>post.jar</code> tool from <code>apache-solr-4.0.0.tgz</code>, and the exact same problem occurs (no data visible in Cassandra, no results for <code>*:*</code> query). For reference, the document was stored in <code>doc.json</code>, the command and output were: <code> java -Dtype=application/json -Durl=http://localhost:8983/solr/resource/initialtiny.solr/update/json -jar post.jar doc.json SimplePostTool version 1.5 Posting files to base url <a href="http://localhost:8983/solr/resource/initialtiny.solr/update/json" rel="nofollow">http://localhost:8983/solr/resource/initialtiny.solr/update/json</a> using content-type application/json.. POSTing file doc.json 1 files indexed. COMMITting Solr index changes to <a href="http://localhost:8983/solr/resource/initialtiny.solr/update/json." rel="nofollow">http://localhost:8983/solr/resource/initialtiny.solr/update/json.</a>. </code> tristanls on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8409 Mon, 14 Jan 2013 17:20:12 +0000 tristanls 8409@http://www.datastax.com/support-forums/ I forgot versions: <code>dse-2.2.1</code> <code>opscenter-2.1.2</code> tristanls on "POST /update/json or /update/xml does not behave as expected" http://www.datastax.com/support-forums/topic/post-updatejson-or-updatexml-does-not-behave-as-expected#post-8408 Mon, 14 Jan 2013 17:18:23 +0000 tristanls 8408@http://www.datastax.com/support-forums/ <code>schema.xml</code> <code> <schema name="initialtiny" version="1.1"> <types> <fieldType name="string" class="solr.StrField"/> <fieldType name="text" class="solr.TextField"> <analyzer> <tokenizer class="solr.StandardTokenizerFactory"/> </analyzer> </fieldType> <fieldType name="uuid" class="solr.UUIDField" multiValued="false"/> </types> <fields> <field name="id" type="uuid" indexed="true" stored="true"/> <field name="body" type="text" indexed="true" stored="true"/> </fields> <defaultSearchField>body</defaultSearchField> <uniqueKey>id</uniqueKey> </schema> </code> <code>solrconfig.xml</code> (the request handler part) <code> <requestHandler name="/update/json" class="solr.JsonUpdateRequestHandler" /> </code> Once these are posted and column families and such are created, this is the end of the output from <code>cassandra-cli</code> <code>describe initialtiny;</code> (this will be relevant further down) <code> ... Column Name: body Validation Class: org.apache.cassandra.db.marshal.UTF8Type Index Name: initialtiny3_solr_body_index Index Type: CUSTOM Index Options: {class_name=com.datastax.bdp.cassandra.index.solr.SolrSecondaryIndex} Compaction Strategy: org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy Compression Options: sstable_compression: org.apache.cassandra.io.compress.SnappyCompressor </code> So, all good so far. I can also view this in OpsCenter, and see that column family was created, etc. When I attempt to add a document for indexing, via: <code>curl <a href="http://localhost:8983/solr/resource/initialtiny.solr/update/json?commit=true" rel="nofollow">http://localhost:8983/solr/resource/initialtiny.solr/update/json?commit=true</a> -H 'Content-Type:application/json' -d '{"id":"aecfd710-5b64-11e2-bcfd-0800205c9a67","body":"This is my awesome text. I hope it gets indexed"}' -v</code> It returns <code>SUCCESS</code>. However, no data is stored in Cassandra, and searching for <code>*:*</code> returns 0 results. What's odd is that running <code>describe initialtiny;</code> within <code>cassandra-cli</code> displays the following at the end: <code> ... Column Name: body Validation Class: org.apache.cassandra.db.marshal.UTF8Type Index Name: initialtiny2_solr_body_index Index Type: CUSTOM Index Options: {class_name=com.datastax.bdp.cassandra.index.solr.SolrSecondaryIndex} Column Name: _solr_update/json Validation Class: org.apache.cassandra.db.marshal.UTF8Type Index Name: solr__solr_updatejson_idx_2 Index Type: CUSTOM Index Options: {class_name=com.datastax.bdp.util.ConfigOnlyIndex, update/json={"id":"aecfd710-5b64-11e2-bcfd-0800205c9a67","body":"This is my awesome text. I hope it gets indexed"} } Compaction Strategy: org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy Compression Options: sstable_compression: org.apache.cassandra.io.compress.SnappyCompressor </code> I was expecting that a document I POSTed would be indexed, and then added to Cassandra datastore. What happened was that the document was not added to Cassandra datastore and querying for <code>*:*</code> results in 0 results. Additionally, the document I posted ends up as <code>Index Options</code> field in column <code>_solr_update/json</code> for some reason. How do I add documents to be indexed and stored by POSTing JSON to Solr?