Hi,
We recently encountered a strange behavior in
lucene v1.4.3 QueryParser: we call
QueryParser.parse("-1", "myidfield", new StandardAnalyzer());
and get retured query as:
-myidfield:1 // apparently we want "myidfield:-1"
Currently we can use TermQuery to avoid QueryParser
to bypass this p
On Oct 7, 2005, at 11:17 AM, Sameer Shisodia wrote:
thnx Erik. Is returning a default constant the answer i'm looking
for ?
Perhaps. Try returning 1.0f - experimentation is always warranted
when playing with scoring tweaks. Have a look at
IndexSearcher.explain() to see why documents sco
: As a new user of Lucene I wonder if anyone can suggest how to do this query
: the fastest way:
Use a RangeFilter instead of a RangeQuery ... the performance will be much
better.
keep in mind that either way you do it, you'll need to store your pathIds
with some sort of padding so that they so
As a new user of Lucene I wonder if anyone can suggest how to do this query
the fastest way:
In the index I got a "content" field with the data, and a "pathID" field
containing an ID ranging from 0 up to possible millions.
In some cases I want to return the documents containing (for example)
thnx Erik. Is returning a default constant the answer i'm looking for ?
btw, the book is kewl :)
sameer
On 10/7/05, Erik Hatcher <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 7, 2005, at 4:14 AM, Sameer Shisodia wrote:
>
> > Hi,
> > Have started using Lucene recently so this might be a oft repeated
> >
Thanks Erik, I tried the reverse index and it worked like a charm.
While I was doing this, we figured out a way to handle contains within
search and wildcard searches at the beginning. I thought I would share
it with the community (and realized it handled the reverse index as
well)
Word: ABCDEFG
Hello,
I have a situation where I wish to open an IndexReader and keep it open. I
never want to add anything to this index but do want to delete from it.
Periodically I would like to flush any deletions that may have been made to
the index to disk (to protect the changes from being lost if the
On Oct 7, 2005, at 4:14 AM, Sameer Shisodia wrote:
Hi,
Have started using Lucene recently so this might be a oft repeated
qn (Do point me to archives if any).
I'm storing multiple values of a field as a comma separated string
during indexing.
Obviously, some docs have more values and some only
We have found the book to be excellent.
http://lucenebook.com/
On 07/10/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Could you tell me where i can find detailed documentation on lucene?
>
> thanks
>
>
-
To unsubscribe, e-m
Could you tell me where i can find detailed documentation on lucene?
thanks
I use my own LSI implementation based on Lucene for text clustering.
I've done some tests, but I do believe that integrating LSI onto the lucene
search subsystem (i.e. creating something like LSISimilarity) is not an easy
task
I start analyzing the documents using Lucene, and then extract tfidf va
Hi,
Have started using Lucene recently so this might be a oft repeated
qn (Do point me to archives if any).
I'm storing multiple values of a field as a comma separated string
during indexing.
Obviously, some docs have more values and some only one and
so hits against those with multiple values for
I've met other persons with such needs and we would also be interested.
Unfortunately, this seems not to be available.
A clear issue might be that LSI, in its original form at least, is
covered by an US patent. But maybe someone finds another form which is
not.
paul
Le 5 oct. 05, à 14:59,
13 matches
Mail list logo
