Ahh, thanks. I might try a basic commit() then and see, although it's not a
huge deal for me. It occurred to me that two optimize() calls would probably
leave exactly the same problem behind.
On 20 May 2011 09:52, Chris Hostetter wrote:
>
> : Thanks for the reply. I'm at home right now, or I'd t
: Thanks for the reply. I'm at home right now, or I'd try this myself, but is
: the suggestion that two optimize() calls in a row would resolve the issue?
it might ... I think the situations in which it happens have evolved a bit
over the years as IndexWRiter has gotten smarter about knowing whe
Thanks for the reply. I'm at home right now, or I'd try this myself, but is
the suggestion that two optimize() calls in a row would resolve the issue?
The process in question is a JVM devoted entirely to harvesting, calls
optimize() then shuts down.
The least processor intensive way of triggering
: http://code.google.com/p/solr-geonames/wiki/DeveloperInstall
: "It's worth noting that the build has also been run on Mac and Solaris now,
: and the Solr index is about half the size. We suspect the optimize() call in
: Embedded Solr is not working correctly under Windows."
:
: We've observed t
Hi All,
Just quick query of no particular importance to me, but we did observe this
problem:
http://code.google.com/p/solr-geonames/wiki/DeveloperInstall
"It's worth noting that the build has also been run on Mac and Solaris now,
and the Solr index is about half the size. We suspect the optimize(
