I noticed if I do the merging in the following way,
IndexWriter.mabyeMerge() is never triggered automatically by the merge
scheduler.
IndexWriter writer = ...;
IndexReader[] readers = ...;
writer.addIndexes(readers)
writer.close();
Is it a bug or by design?
Thanks.
--
Lei
On Thu, Jun 13, 2013 at 7:56 PM, Sriram Sankar wrote:
> Thank you very much. I think I need to play a bit with the code before
> asking more questions. Here is the context for my questions:
>
> I was at Facebook until recently and worked extensively on the Unicorn
> search backend. Unicorn allo
Thank you very much. I think I need to play a bit with the code before
asking more questions. Here is the context for my questions:
I was at Facebook until recently and worked extensively on the Unicorn
search backend. Unicorn allows documents to be ordered by a static rank in
the posting lists
Hi Oliver,
I would like to add a couple of things here..
1. Regarding lengthNorm being called you will also have to make sure that
you set your custom similarity class during index by calling
IndexWriterConfig.setSimilarity(new CustomSimilarity());
2. From what I can see in the source for comput
Hi,
On Thu, Jun 13, 2013 at 8:24 AM, Denis Bazhenov wrote:
> Document id on the index level is offset of the document in the index. It can
> change over time for the same document, for example when merging several
> segments. They are also stored in order in posting lists. This allows fast
> p
