Hi will, others
Thanks for you reply,
As far as I understand it, deleting a document is just setting the deleted
bit, and when segments are merged, then the documents are removed. (not
really sure what this means exactly; I guess the document gets removed from
the store, the terms will no longer
: > The fact that you need to index doc values is related to another change in
: > which we removed Lucene's FieldCache and now recommend to use doc values
: > instead. Until you reindex with doc values, you can temporarily use
: > UninvertingReader[1] to have the same behaviour as in Lucene 4.x.
Hi Rob:
Do you understand how deletes work and how an index is compacted?
There's some configuration/runtime activities you don't mention And
you make testing process sound like a mirror of production? (Including
configuration?)
-will
On 11/5/15 7:33 AM, Rob Audenaerde wrote:
Hi all,
Hi Adrien,
thank you very much for your reply.
> FieldValueQuery is indeed the replacement. I you don't plan on adding other
> clauses to the boolean query, you can even run the FieldValueQuery directly
> through IndexSearcher, without wrapping it in a BooleanQuery.
yes, I have this working now.
Hi all,
I'm currently investigating an issue we have with our index. It keeps
getting bigger, and I don't het why.
Here is our use case:
We index a database of about 4 million records; spread over a few hundred
tables. The data consists of a mix of text, dates, numbers etc. We also add
all these
