Hi,
I use a same instance of writer for multiple threads. It turns out that the
time to finish jobs is more than to create a new writer instance in each
thread. What would be the possible reasons?
Thanks
I tried IndexWriterConfig.OpenMode CREATE, and the size is doubled.
The only way that is effective is the writer's deleteAll() methods.
On Mon, Jan 9, 2012 at 5:23 AM, Ian Lea wrote:
> If you load an existing disk index into a RAMDirectory, make some
> changes in RAM and call addIndexes to add
: The book said that dismax query was similar but different to
:
: DisjunctionMaxQuery
the dismax *parser* in Solr is relatively simple, the majority of the
code in it relates to parsing config options, reporting debugging, etc...
if you wanted to do something similar in non-Solr java code m
Hi House
I had the same problem and tried the same solution, but I am getting an
empty termDocs. How have you done it ?
My code is:
TermDocs td = ir.termDocs();
// Primero los guardo en un temporal porque ponerlos en
un array no puedo
porque me falta la cantidad
On 10/01/2012 10:18, Ian Lea wrote:
If a term has an accent, add both accented and unaccented versions at
index and search time.
So in your example your default field would contain
República Republica
and a search for "República" would expand to "República Republica" and
match both and score h
If a term has an accent, add both accented and unaccented versions at
index and search time.
So in your example your default field would contain
República Republica
and a search for "República" would expand to "República Republica" and
match both and score higher than a search for "Republica" wh
My analyser strips out accents as often these are not entered correctly,
so assume there are two documents in the database with default field
containing
República
Republica
a search for República or Republica will return both results, each with
a score of 1.
Its correct that they both get re
