Hi All,
I have problem when searching terms with wild card and NOT.
Simple Example is,
The query TITLE:(test1234 OR test567) return two results,
the query TITLE:(test1234 OR test567) AND NOT TITLE:(test1234) return one
result as my expectation,
the query TITLE:(test1234 OR test567) AND NOT TIT
: So iterating over and deleting them term by term wouldn't
: preserve the sense of the original query
: (field1:query1 AND field2:query2) OR (field1:query3 AND field2:query4)
Doh! .. you are 100% correct, i am 100% wrong ... i don't know what i was
thinking when i typed that.
the Filter approac
Thanks for your reply. I will answer your questions below one by one:
What is the bigger goal you are trying to get at?
I am trying to implement a "Search System" where we have basically 2 input
queries and output should be chain of documents which connects the 2 input
queries. These chain of d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Grant, dear community
I have written some lines of code to adapt the offset values from Lucene to
values where the terms really appear in the concatenated field value entries.
My tests are successful :)
There are two additional methods inside
Hi Hoss & Erick,
Thx for your responses.
I found the bug in my code. It is not something todo with positions (As I
said in my first mail, I was using right position increments) and also
nothing to do with offsets. Offsets are just ignored, only useful for
Highlighter perhaps. Anyway I am not intere
"karl wettin" <[EMAIL PROTECTED]> wrote:
> I want to set documents in my IndexReader as deleted, but I will
> never commit these deletions. Sort of a filter on a reader rather
> than on a searcher, and no write-locks.
> Perhaps I can pass down a IndexDeletionPolicy to my IndexWriter that
> ignor
Hello all,
What should i do to write a plugin, that extends "QueryFiltes"
and which uses the search results for the given query, to expand the query.
You would have write it, as it doesn't exist in Lucene (but could be
a useful contribution). The easiest version is probably the cosine
similarity, described at http://en.wikipedia.org/wiki/Vector_space_model
Essentially, you have two vectors, and you need to calculate the
cosine of the an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this is the 2.2.0 release
Grant Ingersoll schrieb:
> What version of Lucene are you using?
>
>
> On Aug 17, 2007, at 12:44 PM, [EMAIL PROTECTED] wrote:
>
> Hello community, dear Grant
>
> I have build a JUnit test case that illustrates the prob
