Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: neutral (asf.osuosl.org: 194.52.12.17 is neither permitted nor
 denied by domain of marcus.falck@observer.se)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: SV: Lucene hits.length()
Date: Wed, 9 Aug 2006 15:43:28 +0200
Message-ID: 
 <8834A84C87A2C148AD46921BB8BFC97C021E567A@S1SE1MAIL.emea1.ad.group>
Thread-Topic: Lucene hits.length()
Thread-Index: Aca7uJL+8pOHeqXuTZu2pPNLL/ADqQAAR2/Q
From: "Marcus Falck" <marcus.falck@observer.se>
To: <java-user@lucene.apache.org>

Still worried =3D)
You see it doesn't update the hits.length() in a correct way when I =
create a new searcher. The correct update does just occur in the merges. =
=3D/

-----Ursprungligt meddelande-----
Fr=E5n: Erick Erickson [mailto:erickerickson@gmail.com]=20
Skickat: den 9 augusti 2006 15:34
Till: java-user@lucene.apache.org
=C4mne: Re: Lucene hits.length()

Then you won't see anything added to your index between times. Does this
identify your problem or are you still worried?

Erick

On 8/9/06, Marcus Falck <marcus.falck@observer.se> wrote:
>
> I'm opening a new searcher every 3:rd minute.
>
> -----Ursprungligt meddelande-----
> Fr=E5n: Erick Erickson [mailto:erickerickson@gmail.com]
> Skickat: den 8 augusti 2006 18:58
> Till: java-user@lucene.apache.org
> =C4mne: Re: Lucene hits.length()
>
> I'll take a stab at it.... When are you opening/closing your searcher?
> When
> you open a searcher, you get a snapshot of the index at that instant, =
and
> subsequent modifications aren't visible until you open a new searcher =
(at
> least I think I've got this right).
>
> And I'm sure this also interacts with the writer merge settings
> "interestingly".
>
> Personally, I'd worry about this a lot more if it happened after I'd
> closed
> my writer and opened a new reader <G>...
> Of course, my app has an index that is updated rarely (every two =
weeks),
> so
> I haven't dug into too many details in this area...
>
>
> Best
> Erick
>
> On 8/8/06, Marcus Falck <marcus.falck@observer.se> wrote:
> >
> > I have noticed some strange behavior when searching my lucene index.
> >
> >
> >
> > I'm adding 500.000 docs to an index.
> >
> >
> >
> > MergeFactor =3D 10
> >
> > MinMerge =3D 5000
> >
> >
> >
> > When 49999 have been added ( just before the first 10 * 5000 merge ) =
the
> > hits.length() is reporting around 1000 hits for a keyword (which by =
the
> > way is around the same count as with 5000 docs added). After the =
10*5000
> > merge the hits.length() returns around 8000 hits, which seems to be =
a
> > lot more reasonable. Since I'm adding content in date order ( oldest
> > first ) I have also tried to sort the hits (newest date first) and
> > display the top 10 hits.
> >
> >
> >
> > According to that output it seems that the documents are added
> > correctly.
> >
> >
> >
> > I'm using a multisearcher on top of a RAMDir and an FSDir. Using
> > Lucene1.4.3
> >
> >
> >
> > Anybody that has any idea about why the hit count is so misleading?
> >
> >
> >
> > /
> >
> > Regards
> >
> > Marcus
> >
> >
> >
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org