Evert,
It is definitely not a bug.
I was asking about how to do something, I couldn't quite figure out.
Stop words is the way to go.
David Shifflett
On 7/11/19, 11:26 AM, "evert.wagenaar" wrote:
I see it as a feature, not a bug. The appearance of stop words in the
Search Summary makes i
I see it as a feature, not a bug. The appearance of stop words in the Search
Summary makes it more clear what the Hit is about.Not sure but I think Google
does the same in search summaries.-Evert(http://www.ejwagenaar.com)
Original message From: "Shifflett, David [USA]"
Date: 7
Another +1. We are also big s3 + lucene users and it is very interesting
what other people came up with. We have an S3 lucene directory that allows
immediate read-only use of lucene indexes stored on s3 with simultaneous
local caching and a prototype of segment based index replication based on
the
Note that any other scoring mode (COMPLETE or COMPLETE_NO_SCORES) will
mandatorily visit all hits, so there is no scope of skipping and hence
no point of using impacts.
On Thu, Jul 11, 2019 at 8:51 AM Wu,Yunfeng wrote:
>
>
> @Adrien Grand mailto:jpou...@gmail.com>>. Thanks for your
> reply.
>
>
I just tested this with the search.highight.Highlighter class.
Is this the 'old default highlighter'?
I phrased my question badly.
Of course the stop words shouldn't be highlighted,
as they wouldn't match any query.
My question was really, would the stop words be available for
inclusion in the hi
