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.215.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=T2mby5u6/jDknVK9WquXDhu1PlJVp0N3dCgp3xP8WOetdHj33zxXYm3qiLrE2wepJF
         EG4QulrTE71r1GIMsAGe/wVQoBTod1myZ9La6C4A3CuVdiVchBDNG69oX51zhc9OSn/m
         nZj/VbK1TO+fafUHJRJPgn2Zn3GURJnwhk8v4=
MIME-Version: 1.0
In-Reply-To: <AANLkTikJqgyv3zZ5GSLZHrVLDA9XXyd1Ah98LZ-W9Ovc@mail.gmail.com>
References: <AANLkTin27g2dwfP4GBKKdfAHMBwzqQU_w80J+U+R+JBu@mail.gmail.com>
	<001901cb5d34$92cef3b0$b86cdb10$@thetaphi.de>
	<AANLkTintcq21ULqswpvJuwBiegUGNWcci_m1gm+PQwcz@mail.gmail.com>
	<004301cb5d9e$91a5cfd0$b4f16f70$@thetaphi.de>
	<AANLkTim7qCKop6=P1n=Cq=ZMWUbuoJy5aGMZ3bfExYX9@mail.gmail.com>
	<AANLkTimpjB-SNwx9ZU+Ow=uDf+eCpUuG+2KE-RzbR0op@mail.gmail.com>
	<AANLkTikJqgyv3zZ5GSLZHrVLDA9XXyd1Ah98LZ-W9Ovc@mail.gmail.com>
Date: Tue, 28 Sep 2010 15:26:34 -0400
Message-ID: <AANLkTimSJYn=UhybgxpT5uBhVBekmEdSM8N+PLOJLJqq@mail.gmail.com>
Subject: Re: flushing index
From: Erick Erickson <erickerickson@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=0015174c1724b27455049156d251

--0015174c1724b27455049156d251
Content-Type: text/plain; charset=ISO-8859-1

Nope, never used jNotify, so I don't have any code handy...

Good luck!
Erick

On Tue, Sep 28, 2010 at 9:38 AM, Yakob <jacobian@opensuse-id.org> wrote:

> On 9/28/10, Erick Erickson <erickerickson@gmail.com> wrote:
> > Flushing an index to disk is just an IndexWriter.commit(), there's
> nothing
> > really special about that...
> >
> > About running your code continuously, you have several options:
> > 1> schedule a recurring job to do this. On *nix systems, this is a cron
> job,
> > on Windows systems there's a job scheduler.
> > 2> Just start it up in an infinite loop. That is, your main is just a
> > while(1){}.
> > you'll probably want to throttle it a bit, that is run, sleep for some
> > interval
> > and start again.
> > 3> You can get really fancy and try to put some filesystem hooks in that
> > notify you when anything changes in a directory, but I really wouldn't go
> > there.
> >
> > Note that you'll have to keep some kind of timestamp (probably in a
> separate
> > file or configuration somewhere) that you can compare against to figure
> out
> > whether you've already indexed the current version of the file.
> >
> > The other thing you'll have to worry about is deletions. That is, how do
> you
> > *remove* a file from your index if it has been deleted on disk? You may
> have
> > to ask your index for all the file paths.
> >
> > You want to think about storing the file path NOT analyzed (perhaps with
> > keywordtokenizer). That way you'll be able to know which files to remove
> > if they are no longer in your directory. As well as which files to update
> > when they've changed.
> >
> > HTH
> > Erick
>
>
> I think I'll go with the third option, I had found a class that can do
> monitoring of certain directory, it's called Jnotify. I am planning of
> inserting this class in my code above. can you tell me how to do that?
> or maybe you can forward me to any link tutorials that explain how to
> include Jnotify in a certain lucene source code. I had search about
> Jnotify on google but the tutorials of Jnotify is still a few I guess.
>
> thanks though.
>
> --
> http://jacobian.web.id
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>

--0015174c1724b27455049156d251--