Re: [VuFind-Tech] Inserting a single record

[Demian K. <dem...@vi...>]

Which version of Solr are you using?  Might be helpful to know the exact version so somebody else can attempt to reproduce the same issue under the same conditions....

Also, this may be an obvious question, but have your changes to the indexing rules affected the way unique IDs are determined?  That seems like one possible reason for records not showing up in the index (though it wouldn't explain why a record would fail in isolation but not as part of a group).

Have you done any testing to see how many records it takes to successfully update the index?  i.e. try a batch of 2, a batch of 10, etc.  What if you duplicate the same record multiple times in a file?  Not sure if this will accomplish anything, but it might give you a clue.  It would also be a good way to confirm for certain that a record that fails in isolation definitely succeeds as part of a group (if you haven't already established that fact).

- Demian

From: Greg Pendlebury [mailto:Gre...@us...]
Sent: Tuesday, July 28, 2009 1:55 AM
To: 'vuf...@li...'
Subject: [VuFind-Tech] Inserting a single record


I can't see what I'm doing wrong here, but the same install of solrmarc we use to index the entire catalogue stubbornly refuses to index a single record in isolation.

I've tried adding it to an existing index and I've tried adding it to an empty index.

The marc file is attached (temp.mrc)
And the stdout of solrmarc (with some debugging on the commit) is as well (import_log_stdout.log). It seems to indicate that everything finished without error.

When adding to an old index it creates a new segment (36) but it is zero sized.

When adding to an empty index (the /index directory didn't even exist) it creates the directory and a zero sized segment

I tried Yesterday (and forgot to screencap) outputting the string sent to solr on the insert (updateHandler.addDoc(addcmd)) and it all looks complete. My pet theory is that it's something to do with the flush or commit on a really small data set, and I even tried changing the commit line to "<commit waitFlush='true' waitSearcher='true' />" and I could see the settings change watching jetty's stdout, but no dice :(

I've tried this with several different records and I can't seem to work out what is going on. I'm now looking at installing the latest version of solr under the hood to see if it fixes anything, but has anyone seen this behaviour before? My Google Fu has failed me once again. :(

And our solr/jetty settings are basically straight out of the box, we've only edited our metadata and indexing rules. Any sagely advice would be appreciated because I'm about to break a monitor.

Ta,

Greg Pendlebury
Electronic Services Officer (Systems Team)
Division of Academic Information Services
University of Southern Queensland
Phone: +61 7 4631 1501
Fax: +61 7 4631 1841


________________________________
This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.

The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider of education with the Australian Government (CRICOS Institution Code No's. QLD 00244B / NSW 02225M)