This article on optimistic concurrency: http://heliosearch.org/solr/optimistic-concurrency/
explains (I believe) exactly what's going on... In SolrLogger.java, the .csv files created for insertion into the new shared indexes are composed using ALL fields -- including _version_. Any NEW document with a _version_ field will fail on update. Or am I misunderstanding something? If this is the case, I think one solution may be to specify a field list (excluding version) when querying solr by date during the creation of the filesToUpload List. The other solution would be to drop the _version_ field from schema.xml (and turn off the update log in solrconfig.xml), and optimize to drop the field. I'm not sure what this adds in terms of an insert-only index anyway. Thoughts? Cheers! Bill ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
