Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (hermes.apache.org: domain of radomirml@gmail.com
 designates 64.233.184.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=By24bTH7bhsXQ587WdBRpbd8NayvosAMy4Pmbc0/ht5Avx6biDQTL2ZAi/l3N6GQpETZkHTIvESIYrfscT7IE+lUW/js1RAPp5LFovtDewHcDhIxItX9giH1H8ZvM6DuikyzX7uYp+MGNiqkE314Kyk33fDf7p1xn0SSe7AmPeI=
Message-ID: <4ed277ec050606003884fe14d@mail.gmail.com>
Date: Mon, 6 Jun 2005 09:38:58 +0200
From: Radomir Mladenovic <radomirml@gmail.com>
Reply-To: Radomir Mladenovic <radomirml@gmail.com>
To: java-dev@lucene.apache.org
Subject: Re: patch: adding IndexReader.isCurrent()
In-Reply-To: <20050603222925.2014.qmail@web31106.mail.mud.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <200506040005.03731@danielnaber.de>
	 <20050603222925.2014.qmail@web31106.mail.mud.yahoo.com>

Method isCurrrent() is a useful addition and I'm glad fix with
timestamp use for initial version is finally commited. However,
although version is not meaningful, I believe it should stay in API...

The software I'm working on is using pair "version, document_id" as a
fast reference to lucene document - if version is not current we have
to make an additional query first in order to get document id. Without
version information method isCurrent() is useless in this context as
we don't know which version of search results client has.

Here's one simple example... Let's say we have web application that's
paging search results (20 or so per page) and we re-run query for each
"next results page" request. Without version information, how can we
eventually warn user that index changed between its two "next results
page" requests?

So I think getCurentVersion() should stay and (as I suggested earler)
would like to see getVersion() added to IndexReader.

In addition, shouldn't SigmentInfos.readCurrentVersion() rely on
commit lock when reading segments file? Could someone with deeper
understanding of lucene internals check this?

Radomir


On 6/4/05, Otis Gospodnetic <otis_gospodnetic@yahoo.com> wrote:
> Well, Radomir, the person who asked about that method should be on
> java-dev@, so I'll assume he'll speak up if he needs that method.  I
> think isCurrent() is good to go.
>=20
> Otis
>=20
>=20
> --- Daniel Naber <lucenelist@danielnaber.de> wrote:
>=20
> > On Friday 03 June 2005 23:51, Otis Gospodnetic wrote:
> >
> > > Isn't version a time stamp now?
> >
> > It starts as a time stamp, but then +1 is added for each change. So
> > that
> > number has no useful meaning I think. It's only useful for
> > comparison. Or
> > am I missing something?
> >
> > Regards
> >  Daniel
> >
> > --
> > http://www.danielnaber.de
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-dev-help@lucene.apache.org
> >
> >
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>=20
>

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