On 3/7/07, Jeff Rodenburg <[EMAIL PROTECTED]> wrote:
Oops, my bad I didn't see either 186 or 187 before entering 188. :-)
I have closed SOLR-186 and SOLR-187 as duplicates, please add relevant
info to SOLR-188 if needed.
-Bertrand
m: 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
f 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: R
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.
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 e
: 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/optimi
