Ok let me explain you. By warming up the reader i used to understand is that
it memorizes the index terms. Therefore subsequent queries will be answered
by using these terms. Is this correct ?
On 9/18/07, Karl Wettin <[EMAIL PROTECTED]> wrote:
>
>
> 18 sep 2007 kl. 08.33 skrev Shailendra Mudgal:
18 sep 2007 kl. 08.33 skrev Shailendra Mudgal:
Whether it caches frequently used terms ?
I don't understand you question?
--
karl
On 9/18/07, Karl Wettin <[EMAIL PROTECTED]> wrote:
18 sep 2007 kl. 07.12 skrev Shailendra Mudgal:
What my goal is to understand the caching strategy.
Whether it caches frequently used terms ?
On 9/18/07, Karl Wettin <[EMAIL PROTECTED]> wrote:
>
>
> 18 sep 2007 kl. 07.12 skrev Shailendra Mudgal:
>
> >
> > What my goal is to understand the caching strategy. How well this
> > work for repetitive queries. Is there any room available to improve
>
18 sep 2007 kl. 07.12 skrev Shailendra Mudgal:
What my goal is to understand the caching strategy. How well this
work for repetitive queries. Is there any room available to improve
this.
It is usually a loss of resources to cache results in a busy system
with gaussianity distributed q
Hi Yonik,
Thanks for your response. I'll feel great if you can explain this in more
detail as i am not sure that whether i have understood this correctly or
not. Or if you can direct me to some resource that will also be very good
for me.
What my goal is to understand the caching strategy. How w
: Lucene has historically taken the exact opposite approach... open up the API
: as needed. Unless there is very good reason for it, classes and data should
: be kept private.
Just to clarify the reasoning behind this: once something is made public,
the API has to be supported in perpetuity --
Cedric,
On Sep 17, 2007, at 11:54 AM, Erik Hatcher wrote:
On Sep 17, 2007, at 6:51 AM, melix wrote:
I've faced the very same problem with NearSpansOrdered and so on.
I think
unless there is a very good reason for it, classes should be made
public,
this would at least make the "delegate" d
On 9/17/07, Shailendra Mudgal <[EMAIL PROTECTED]> wrote:
> One thing that i understand about IndexReader is that for subsequent
> queries, results come fast as the IndexReader needs to be warmed up.
> According to this, I am trying to find out the answers of following
> questions :
> - is there any
On Sep 17, 2007, at 6:51 AM, melix wrote:
I've faced the very same problem with NearSpansOrdered and so on. I
think
unless there is a very good reason for it, classes should be made
public,
this would at least make the "delegate" design pattern available.
Lucene has historically taken the
On Monday 17 September 2007 11:40, Mohammad Norouzi wrote:
> Hi
> I have a problem in getting correct result from Lucene, consider we have an
> index containing documents with fields "field1" and "field2" etc. now I want
> to have documents in which their field1 are equal one by one and their
> fie
Take the comma out of: | <#P: ("_"|"-"|"/"|"."|",") > in the .jj file
(around line 92). Keep in mind that this will affect being able to find
tokens that where previously indexed with the comma there (obviously). I
believe the javacc target in the build file will rebuild...you need to
get javac
Hi,
Standard tokenizer works pretty well for me... but i found one problem with my
usage...
I want to tokenize..."TheRing6,Proposal6,GuyandGirl6" as a three saparate
tokens.. while standard analyzer considering it as a one word because it has
one digit in token.
Expected three tokens:
1. ther
As I mentioned, IndexReader is the one that holds the memory. You should
explicitly close the underlying IndexReader to make sure that the reader
releases the memory.
Sebastin wrote:
>
> Hi testn,
> Every IndexFolder is of size 1.5 GB of size,eventhough when
> i used to Open and
Hi All,
One thing that i understand about IndexReader is that for subsequent
queries, results come fast as the IndexReader needs to be warmed up.
According to this, I am trying to find out the answers of following
questions :
- is there any caching is done in lucene for search ?
- if yes, is it fo
Thanks Paul. I'm doing something very similar, but I'd like to notice that it
is very hard to "extend" Lucene without breaking compatibility. I mean I
have written classes that expand SpanQueries, but, for example, and to my
mind not understandable, classes like "BooleanWeight" are package protect
I want to sort results of a query according to a specific field(date).I have
a parallelMultiSearcher with some underlying remote searchers. Indexes in
remote searchables are large and enabling sort will make searching slow. As
I understood from previous threads, a solution is: searching without so
Hi
I have a problem in getting correct result from Lucene, consider we have an
index containing documents with fields "field1" and "field2" etc. now I want
to have documents in which their field1 are equal one by one and their
field2 with two different value
to clarify consider I have this query:
17 matches
Mail list logo
