Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: domain of erickerickson@gmail.com
 designates 209.85.134.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=FqY+BR9NS4hqBBIks/GI6eTjwQkZtJkR5N7OnbWSUksXBp4fTY1fH45t+YztV7wN7kwzZ4vU0hUtKXxNTwRyKWst0jFQanFTupLefYi3ykC/0UO6F42UIC7sTrBvsDk1u953jwM6+6pR9wQRitJMzSJc+cdjVZyIv+zdlUc9wNk=
Message-ID: <359a92830705241305h2aa4cd85pea7fde5b28c5213e@mail.gmail.com>
Date: Thu, 24 May 2007 16:05:48 -0400
From: "Erick Erickson" <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Subject: Re: maxDoc and arrays
In-Reply-To: <7798eaa0705241130q2258caf5rd2d5486c1f6afa66@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_87585_21143010.1180037148306"
References: <7798eaa0705240941y5b420dd3sb2867ed86008dc19@mail.gmail.com>
	 <359a92830705241025t583bb657jbde1a1776bc1546a@mail.gmail.com>
	 <7798eaa0705241130q2258caf5rd2d5486c1f6afa66@mail.gmail.com>

------=_Part_87585_21143010.1180037148306
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Document IDs will be re-utilized, after, say, optimization.
One consequence of this is that optimization will change the IDs
of *existing* documents.

You're right, that numdocs may well be shorter than maxdocs.
That's what I get for reading quickly...

Best
Erick

On 5/24/07, Carlos Pita <carlosjosepita@gmail.com> wrote:
>
> >
> >
> > No. It will always be at least as large as the total documents. But that
> > will also count deleted documents.
>
>
>
> Do you mean that deleted document ids won't be reutilized, so the index
> maxDoc will grow more and more with time? Isn't there any way to compress
> the range? It seems strange to me, considering that an example in the book
> suggests to use the document id as an array index for an array of maxDoc
> elements.
>
> Cheers,
> Carlos
>
> Why wouldn't numdocs serve?
> >
> > Best
> > Erick
> >
> >
> > The motivation of this question is that I want to associate some info to
> > > each document in the index, and in order to access this additional
> data
> > in
> > > O(1) I would like to do this through an array indexing. But the array
> > size
> > > shouldn't be a lot greater than the total number of documents. I see
> > that
> > > something similar is done in the example of section 6.1 of Lucene in
> > > Action,
> > > but for sorting purposes, which is not my case.
> > >
> > > Related to this: how can update my array of extra data when documents
> > are
> > > added/removed to/from the index? Is there any feedback mechanism by
> > means
> > > of
> > > callbacks or event handlers?
> > >
> > > Thank you in advance.
> > > Regards,
> > > Carlos
> > >
> >
>

------=_Part_87585_21143010.1180037148306--