Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of erickerickson@gmail.com
 designates 209.85.216.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=LQ7AfBA2Q5tpxBcTXpnNmTrky7Jyj28zdgHCHmSKj03Sx4je/gtsLtqH9NmkuiYppU
         /eIpdPdYWgadJ9BZG49aAdjC4SiJql+Hie1r3z6AsFbWOtapN5EMpEx04vEt4HRSOz92
         yWuh2vHaabYqKtthg0q5Xmty9bJk7S2i/8HC8=
MIME-Version: 1.0
In-Reply-To: <AANLkTinwnP+_DU1sPiWOk2P4+N+a=JosM7K=KaDZ8Tp9@mail.gmail.com>
References: <AANLkTimm69AuyOwB03qSahOCUE3vwW3kBJJzf-91YoRU@mail.gmail.com>
	<alpine.DEB.1.10.1012132251230.18109@radix.cryptio.net>
	<AANLkTinwnP+_DU1sPiWOk2P4+N+a=JosM7K=KaDZ8Tp9@mail.gmail.com>
Date: Tue, 14 Dec 2010 10:45:52 -0500
Message-ID: <AANLkTi=f2d6jr0UCif8qWG5SiKD6hDMavjA_3AKNMLoo@mail.gmail.com>
Subject: Re: Forcing specific index file names
From: Erick Erickson <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=0016363b8efc25efe8049760b75f

--0016363b8efc25efe8049760b75f
Content-Type: text/plain; charset=ISO-8859-1

I'm missing something here. You mention "two versions of
a data set in a directory tree structure". The Lucene indexes
will have different names if they have been merged. Usually
this is a result of changing the data, issuing an optimize, etc.
That is, the data *is* different so it seems perfectly appropriate
to consider them new...

Lucene never changes an existing segments file once it is committed.
It only merges segments then deletes the old ones. So if the file names
are different, then it seems that renaming them wouldn't be what you
really want.

So either it really is an XY problem (as in "I really don't think you want
to do that") or I completely  misunderstand what
you're trying to do.

Best
Erick

On Tue, Dec 14, 2010 at 9:46 AM, Earl Hood <earl@earlhood.com> wrote:

> On Tue, Dec 14, 2010 at 12:53 AM, Chris Hostetter
> <hossman_lucene@fucit.org> wrote:
> >
> > : It is possible to always have Lucene end up with the
> > : same set of index filenames for each index generation
> > : process?
> >
> > this smells like an XY problem .... why do you car what the file names
> > are? that's an implementtaion detail of lucene -- the directory as a
> whole
> > is the index -- what are you trying to do that you are concerned about
> > wanting to "rename" the files?
>
> I have to create patch sets against two version of a data
> set in a directory tree structure, and the data set contains
> a lucene index.
>
> However, if the filenames are not consistent for the index,
> then the delta program thinks they are completely new
> files vs just doing an xdelta on the index data.
>
> If renaming is not possible, the delta program will
> have to have lucene awareness about variations in
> the filenames between two versions of a data set
> tree.  I guess I will have to do this if I am going
> to be lectured about how to develop software.
>
> From a design perspective, I figured if the process
> that builds the data sets and the lucene index can
> be modified to make sure the lucene index files are
> consistently named, the delta computation program
> can stay agnostic about lucene and just do a basic
> tree differencing algorithm.
>
> --ewh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--0016363b8efc25efe8049760b75f--