It doesn't appear to be working: Sending URI: http://text4:8983/solr/@10324_1_155/update Sending Content: <?xml version='1.0' encoding='UTF-8'?> <commit/>
This multi core update request to commit the data doesn't change the numDocs of the core :-/ hmm and the response was interesting: Response: <?xml version="1.0" encoding="UTF-8"?> <response> <lst name="responseHeader"><int name="status">0</int><int name="QTime">5</int></lst><str name="WARNING">This response format is experimental. It is likely to change in the future.</str> </response> Any thoughts? Best Regards, Martin Owens -----Original Message----- From: Stu Hood [mailto:[EMAIL PROTECTED] Sent: Mon 1/28/2008 5:10 PM To: solr-user@lucene.apache.org Subject: RE: Indexing Directly, searching with solr Performing a '<commit/>' command on the Solr server will force it to open a new IndexReader, and make your changes visible. Thanks, Stu -----Original Message----- From: "Owens, Martin" <[EMAIL PROTECTED]> Sent: Monday, January 28, 2008 5:38pm To: solr-user@lucene.apache.org Subject: Indexing Directly, searching with solr Hello all, In order to get around problems with Solr indexing very large files (mostly memory issues, not being able to deal with streams, not being able to handle file pointers and handling everything in java as huge strings) we've decided to index using lucene directly. Now we have an index created, but Solr just doesn't see any documents there, even though we know there are documents indexed and the segments and cfs contains data. Any thoughts? Best Regards, Martin Owens
