Have you looked here for ideas?
http://wiki.apache.org/lucene-java/ImproveSearchingSpeed
Best
Erick
On Sat, Oct 17, 2009 at 11:03 AM, mitu2009 wrote:
>
> Hi,
>
> I need to improve performance of my Lucene search query. Can I use
> RAMDirectory?Does it optimize performance?Is there any index si
Hi,
I have written a my own weighted synonym filter and tried to integrate it
inside an analyzer.
The analyzer as defined in the schema.xml is:
the field type is
*
**
*
Th
I am a bit stumped by how to ensure that, where there are multiple terms in
my query, that each term must appear at least once across all specified
fields of my document. I am using MultiFieldQueryParser and
BooleanClause.Occur.SHOULD in the query; I tried putting all fields into a
single giant fi
Hi,
you should probably ask your self why your performance is bad before
looking at solving it by scaling hardware. I.e. what are your
application needs, how so you solve you needs at index/query time and
how can you replace this with something better? If you tell us a bit
more about your
Hi,
I need to improve performance of my Lucene search query. Can I use
RAMDirectory?Does it optimize performance?Is there any index size limit for
this? I would appreciate if someone could list pros and cons of using a
RAMDirectory.
Thanks.
--
View this message in context:
http://www.nabble.co
We do not need any 1.6 language features for Lucene (we do not use
annotations at all).
And: The current 1.6 JVM has still lots of bugs, so e.g. we use still 1.5
for all Lucene related code. The most important thing for Lucene 3.0 are
things like StringBuilder and Generics, which is all covered by
On Fri, Oct 16, 2009 at 12:31 PM, Grant Ingersoll wrote:
>
> On Oct 16, 2009, at 6:05 AM, Uwe Schindler wrote:
>
>> I would recommend to adopt your app to 2.9 and enable deprecation
>> warnings.
>> As soon as all deprecation warning disappear during compile, you are able
>> to
>> just go to 3.0 (j
hi
I am wondering what is the difference between
collector.getTotalHits();//where collector is a TopScoreDocCollector
(which returns the correct value for my example = 2 docs)
and
collector.topDocs().totalHits (which returns 0, and is wrong)
the collector was used in a search: searcher.search
OK then this is exactly what was happening with LUCENE-1573 -- Lucene
was not properly handling the interrupt request, and instead of
throwing an exception, entered a spin loop that starves the merge
threads.
Can you try 2.9.0 (and turn back on your Future.cancel(true) call) and
see if it's fixed?
Hi,
On Fri, Oct 16, 2009 at 9:12 PM, Grant Ingersoll wrote:
> I'm not aware of any, but you might get more mileage asking on java-user.
You're right, poor original choice of list from me.
java-users@, here's my question from java-dev@:
Some while ago I implemented a simple JDBC to JCR bridge [
10 matches
Mail list logo