Dear All,
We have been using the highlighter from the lucene sandbox, which works
very nicely most of the time. However when we try and use it with a
prefix query (which is what you get having parsed a wild-card query), it
doesn't return any highlighted sections. Has anyone else experienced
this p
I understand that unlike relational database, Lucene is flexible in having
documents with different set of fields. My index has documents with a date
and content field. There are also a few book keeping documents that does
not have the date field. Things work well except in one case:
Sort
Hi:
Is there way to find out given a hit from a search, find out which
fields contributed to the hit?
e.g.
If my search for:
contents1="brown fox" OR contents2="black bear"
can the document founded by this query also have information on
whether it was found via contents1 or contents2 or bot
On Feb 16, 2005, at 21:28, Yura Smolsky wrote:
Well, I have not 6 CPU in one box :)
What about 6 boxes with 1 CPU each :P
Cheers
--
PA, Onnay Equitursay
http://alt.textdrive.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Hello, Erik.
EH> Are you using multiple IndexSearcher instances?Or only one and
EH> sharing it across multiple threads?
EH> If using a single shared IndexSearcher instance doesn't help, it may be
EH> beneficial to port your code to Java and try it there.
I have single instance of IndexSearch
Hello, PA.
>> Does anyone here have experience in handling big indexes with many
>> threads?
P> What about turning the problem around and spitting your index in
P> several chunks? Then you could search those (smaller) indices in
P> parallel and consolidate the final result, no?
Well, I have not
Are you using multiple IndexSearcher instances?Or only one and
sharing it across multiple threads?
If using a single shared IndexSearcher instance doesn't help, it may be
beneficial to port your code to Java and try it there.
I'm just now getting into PyLucene myself - building a demo for a
On Feb 16, 2005, at 21:04, Yura Smolsky wrote:
Does anyone here have experience in handling big indexes with many
threads?
What about turning the problem around and spitting your index in
several chunks? Then you could search those (smaller) indices in
parallel and consolidate the final result, n
Hello.
I use PyLucene, python port of Lucene.
I have problem about using big index (50Gb) with IndexSearcher
from many threads.
I use IndexSearcher from PyLucene's PythonThread. It's really a wrapper
around a Java/libgcj thread that python is tricked into thinking
it's one of its own.
The core o
But all write access to the index is synchronized, so that although multiple
threads are creating an IndexWriter for the same directory and using it to
totally recreate that index, only one thread is doing this at once.
I was concerned about the safety of using an IndexSearcher to perform
queries
Hi Paul,
If I understand your setup correctly, it looks like you are running
multiple threads that create IndexWriter for the ame directory. That's
a "no no".
This section (first hit) describes all various concurrency issues with
regards to adds, updates, optimization, and searches:
http://www
Hi,
I've read from various sources on the Internet that it is perfectly safe to
simultaneously search a Lucene index that is being updated from another
Thread, as long as all write access to the index is synchronized. But does
this apply only to updating the index (i.e. deleting and adding docume
On Wednesday 16 February 2005 06:49, Owen Densmore wrote:
> > From: Erik Hatcher <[EMAIL PROTECTED]>
> > Date: February 12, 2005 3:09:15 PM MST
> > To: "Lucene Users List"
> > Subject: Re: Multiple Keywords/Keyphrases fields
> >
> >
> > The real question to answer is what types of queries you're p
13 matches
Mail list logo
