> coord() and queryNorm() work on the query as a whole, which may span
> multiple fields.
Thanks for the response, but I'm still confused. In our use case, our
documents have two distinct types of fields, e.g.
Document:
A-field1
A-field2
A-field3
B-field1
B-field2
B-field3
In our ap
We recently upgrade our lucene library from 1.9.1 to 3.6.1 and we run into
multiple AlreadyClosedException when doing search. Here is the stack:
RetrievedDateMarker=2012-11-08 08:36:34.393 Error searching
\\p7na02b\na01_mail03\index\daily\20121031.main.index.3
com.seccas.task.SearchRequest
Having played with merge parameters and various index parameters, it seems
possible to change the I/O usage at the cost of the number of index files.
However, it does appear that this version of lucene is using more CPU. Is
there any reason for this ? is it normal ? We can push a large amount o
Thank you for the tips. I looked at the index and the query and nothing
seemed to be wrong. Then I realized that someone put a condition in the
code after getting the results of the query. this condition removed docs
which did not contain the exact words of the query. This condition was
case se
I modify TopDocsCollector and collect some to-score value store in index to
an array and then calculate them with similar score,return final score to
sort the docs.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Document-scoring-tp4018582p4018962.html
Sent from the Lucene
