Hi,
- if you want to search for those both words next to each other, use a phrase
query. This is by putting quotes around, QueryParser will parse this to a
Lucene PhraseQuery
- If you don't want to have a phrase and just want to ensure that both words
must be in the document, prefix both words
Hi,
When I search two words separated by a space, the search returns results
consisting of the two word pattern and also searches the individual words
separately.
I don't have the code in front of me at the moment to give you my code snippet,
but I can tell the following.
I use the standard
(13/07/11 22:56), gtkesh wrote:
Hi everyone! I have two questions:
1. What are the cases where Lucene's default tf-idf overperforms BM25? What
are the best use cases where I should use tf-idf or BM25?
2. Are there any user-friendly guide or something about how can I use BM25
algorithm instead
Hi everyone! I have two questions:
1. What are the cases where Lucene's default tf-idf overperforms BM25? What
are the best use cases where I should use tf-idf or BM25?
2. Are there any user-friendly guide or something about how can I use BM25
algorithm instead of Lucene's default tf-idf? I trie
Can someone please provide clarification on this?
-
Thanks
-K'Rider
--
View this message in context:
http://lucene.472066.n3.nabble.com/SurroundQueryParser-Please-help-with-Syntax-tp4076302p4077248.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
-
On 07/11/2013 09:59 AM, Ankit Murarka wrote:
> Say, suppose I send a Message X. The contents of the message X is
> stored. Now, for each incoming message I will compare the contents
> with the message X. If the content is equal I will increment the
> counter and when it reaches say 100, I will not
Say, suppose I send a Message X. The contents of the message X is
stored. Now, for each incoming message I will compare the contents with
the message X. If the content is equal I will increment the counter and
when it reaches say 100, I will not allow more processing of messages.
For each mess
Please post the code of your TokenStream(s) thats behind this analyzer? The bug
is there (and it is a bug, if it is not working correctly). The Lucene internal
analyzers don't have this problem, as the TokenStreams behind that are
implemented and tested. In most cases those problems appear, if t
Hi all,
I'm migrating from Lucene 3.6.1 to 4.3.1 and there seems to be a major
change in how analyzers work
Given the code example below (which is almost copied from
http://lucene.apache.org/core/4_3_1/core/index.html)
@Test
public void testAnalysis() throws IOException {
final Strin
