From: Demian K. <dem...@vi...> - 2013-04-17 18:59:25
|
Thanks for the update/clarification. Unfortunately, I just downloaded the 2.5.1 binary from the googlecode site, and it's still not working for me with Solr 4.1. When I try to index a set of records in direct write mode, SolrMarc hangs indefinitely. If I kill the process, then it spits out an exception: Exception in thread "main" java.lang.reflect.InvocationTargetException ... Caused by: java.lang.NoSuchMethodError: org.apache.solr.update.AddUpdateCommand: method <init>()V not found This appears to be the same situation I was encountering with earlier versions of SolrMarc. (Also, for the record, I tried pulling the latest code from Subversion and rebuilding from source... but I get exactly the same error). thanks, Demian > -----Original Message----- > From: Robert J. Haschart [mailto:rh...@vi...] > Sent: Wednesday, April 17, 2013 11:18 AM > To: sol...@go...; Demian Katz > Subject: Re: [solrmarc-tech] Solr 4 + SolrMarc status check > > Demian, > > 1) Some progress has been made on Solr 4 direct writing. It works, but > with the caveat that binary data (end-of-subfield, end-of field, and end-of > record markers) will be represented as  which I believe that VuFind is > already capable of handling. I haven't yet made any attempt to fix the > patch that is needed to handle binary direct writes. > > 2) > Is this all tied to the use_streaming_proxy setting, or does it affect > all HTTP writes? Is there a way to implement a completely serial, > one-record-at-a-time HTTP method to ensure accuracy at the expense of speed? > > Yes. This only occurs when using the streaming proxy server. It seems to > be endemic to the design of how the streaming proxy is implemented. Several > people pushed for the streaming proxy being able to be used, in the hopes > that it might be faster, and I made it the default method of operation. > However I have since made the non-streaming HTTP version the default, > because of this unreliability. So if you specify > solrmarc.use_streaming_proxy = false or even simply not specify > solrmarc.use_streaming_proxy = true then the serial, one-record-at-a-time > HTTP communication will be used, and the dropped record batches problem will > be avoided. > > The code with these changes is available vie the solrmarc.googlecode.com > website. > > -Bob Haschart > > > On Tue, 16 Apr 2013 15:59:43 +0000 > Demian Katz <dem...@vi...> wrote: > > Sorry if I should have a better understanding/memory of where things > >stand... but following today's developers call, I thought a status check > >would be in order. > > > > Currently, we're in a holding pattern on moving forward to Solr 4 in > >VuFind because we want to be sure we have SolrMarc compatibility. My > >understanding is that right now, the main issue is the direct index > >writing. > > > > So two questions: > > > > > > 1.) Has any progress been made on Solr 4 direct writing? If not, are > >there plans to implement it, or will the feature be deprecated? > > > > > > > > 2.) Assuming that direct writing will not be implemented (or will no > >longer be recommended), are there still outstanding issues with the HTTP > >method dropping batches without warning? See this thread: > >https://groups.google.com/forum/#!msg/solrmarc-tech/25L-srcaoeY/Head3xvXjwQJ > >-- I don't see any final resolution on that (Naomi says something about > >Solr 3.6 helping, but it doesn't feel like it could fully address the > >underlying problem). Is this all tied to the use_streaming_proxy setting, > >or does it affect all HTTP writes? Is there a way to implement a > >completely serial, one-record-at-a-time HTTP method to ensure accuracy at > >the expense of speed? > > > > > > Tod has volunteered to provide some sample record sets to help reproduce > >the HTTP-related errors if necessary... and I'm willing to look at code if > >there's work I can help with (though I don't exactly know what needs to be > >done at this point). > > > > Bottom line: I either need index writing to move forward, or if I need to > >switch the VuFind standard configuration to use HTTP, I want to be sure > >that's not going to cause hard-to-diagnose indexing problems for anyone. > > > > thanks, > > Demian > > > > -- > > You received this message because you are subscribed to the Google Groups > >"solrmarc-tech" group. > > To unsubscribe from this group and stop receiving emails from it, send an > >email to sol...@go.... > > To post to this group, send email to sol...@go.... > > Visit this group at http://groups.google.com/group/solrmarc-tech?hl=en. > >For more options, visit https://groups.google.com/groups/opt_out. > > > > |