I'm using apache commons pooling library to pool the IndexSearcher, so that
my system
can provide high performance.
I wonder if it is reasonable to pooling objects of lucene?
If yes, is there any other objects I can also pool?
Thank you!
system needs to use (in the basic
sense). Pooling multiple instances pointing to the same index won't
benefit your performance. Things get trickier when you are updating
the index and want to see the updates.
Erik
On May 19, 2006, at 5:13 AM, Zhenjian YU wrote:
> I'm
OK, got it. Thanks.
On 5/23/06, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On May 21, 2006, at 10:56 PM, Zhenjian YU wrote:
> I didn't dig the source code of lucence deep enough, but I noticed
> that the
> IndexSearcher uses an IndexReader, while the cost of initializing
&g
hi, *vikas,
*the ajax way should work for you.
while in the lucene part, you should do something to handle the prefix
query.
Best Regards,
Zhenjian
On 5/24/06, Vikas Khengare <[EMAIL PROTECTED]> wrote:
Hi Friend
I want to perform search like "Google search" which will give
tarting with "a".
Either way is a solution.
Best Regards,
Zhenjian
On 5/24/06, Vikas Khengare <[EMAIL PROTECTED]> wrote:
Hi Zhenjian YU
I have implemented that with AJAX Search But when I type "*a*" in
textbox. It gives me all results which contains letter &
yes, PrefixQuery will help.
On 5/24/06, mark harwood <[EMAIL PROTECTED]> wrote:
>>What will happen if I send PrefixQuery
A search returns a list of docs - you want a list of
words which is why I suggested using the IndexReader
"terms" APIs which PrefixQuery uses internally.
If you are not in
