Hi folks,
we really like the flexible QueryParser. We already used it for a Verity-Syntax
Parser and it worked well.
But now we want to use the Standard-Lucene-Syntax with some additions.
Can we trust in StandardQueryParser or should(must) we use the classic
QueryParser?
For project safety we
Dear Carsten,
abstract of your post:
you need the offset to perform your search/ranking like the position is needed
for phrase queries.
You are using reader.getTermFreqVector to get the offset.
This is to slow for your application and you think about a switch to version 4.0
imho you should usi
Dear Carsten,
your question was about the purpose of the offset-Attribute and the
reader.getTermFreqVector method.
You have asked because this method is not very fast.
imho main reason for TermFreqVectors is highlighting.
(FastVectorHighlighter and DefaultSolrHighlighter#doHighlightingByHighligh
Hi 惠达 王,
if you do not sort (by field values) and do not use faceted search or joins the
field cache will not be used.
If you want to go sure:
Write a MockFieldCache and call FieldCache.DEFAULT = new MockFieldCache();
Best regards
Karsten
btw. the are other objects in the main-memory like do
