Apologies in advance if SOLR-187 and SOLR-188 look the same -- they are the same issue. I have been using adjusted scripts locally but hadn't used Jira before and wasn't sure of the process. I decided to figure it out after answering Gola's question this morning...then saw that Jeff had mentioned a similar issue last night. I apologize again for confusion over the double entry.
Thanks, -Graham > -----Original Message----- > From: Jeff Rodenburg [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 06, 2007 4:34 PM > To: solr-user@lucene.apache.org > Subject: Re: Error with bin/optimize and multiple solr webapps > > This issue has been logged as: > > https://issues.apache.org/jira/browse/SOLR-188 > > A patch file is included for those who are interested. I've > unit tested in my environment, please validate it for your > own environment. > > cheers, > j > > > > On 3/5/07, Jeff Rodenburg <[EMAIL PROTECTED]> wrote: > > > > Thanks Hoss. I'll add an issue in JIRA and attach the patch. > > > > > > > > On 3/5/07, Chris Hostetter <[EMAIL PROTECTED] > wrote: > > > > > > > > > : This line assumes a single solr installation under > Tomcat, whereas > > > the > > > > > > : multiple webapp scenario runs from a different location > (the "/solr" > > > part). > > > : I'm sure this applies elsewhere. > > > > > > good catch ... it looks like all of our scripts assume > > > "/solr/update" is > > > > > > the correct path to POST commit/optimize messages to. > > > > > > : I would submit a patch for JIRA, but couldn't find these files > > > under version > > > : control. Any recommendations? > > > > > > They live in src/scripts ... a patch would ceritanly be > apprecaited. > > > > > > FYI: there is an evolution underway to allow XML based update > > > messages to be sent to any path (and the fixed path "/update" is > > > being deprecated) so it would be handy if the entire URL path was > > > configurable (not just hte webapp name) > > > > > > > > > -Hoss > > > > > > > > >
