Not at the moment.
Actually, I'm already working on a remote copy utility for gaevfs that will
upload large files and folders but the first cut is about a week away.
- Original Message
> From: Dvora
> To: java-user@lucene.apache.org
> Sent: Thursday, September 10, 2009 2:18:35 PM
> Su
Another alternative is storing the indexes in the Google Datastore, I think
Compass already supports that (though I have not used it).
Also, I have successfully run Lucene on GAE using GaeVFS
(http://code.google.com/p/gaevfs/) to store the index in the Datastore.
(I developed a Lucene Directory
Tue, Sep 1, 2009 at 9:04 AM, Shai Erera wrote:
> > If I'm not mistaken, IndexReader reads the .del file into memory, and
> > therefore subsequent updates to it won't be visible to it.
> >
> > Shai
> >
> > On Tue, Sep 1, 2009 at 3:54 PM, Ted Stockwell
e I'm wondering if I'm missing something...
Thanks,
ted stockwell
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
ended to run it during weekends, since the
> optimize() process itself may take several hours, so that a nightly job
> won't be enough.
>
> Shai
>
> On Mon, Aug 31, 2009 at 6:25 PM, Ted Stockwell wrote:
>
> > Hi All,
> >
> > I am new to Lucene and I was
s indexing slower.
However, the book does not explain *why* indexing would be slower while
optimizing.
Since I know that optimization will create new segments and not mess with the
old ones, I'm confused as to how optimizing may cause indexing to slow down.
Any ideas?
Thanks
