lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From eks dev <>
Subject Re: Polymorphic Index
Date Fri, 22 Oct 2010 13:56:23 GMT
I do not think aeletes are really a problem, there are probably many ways to fix 
that. The problem is to create and keep in sync two(or more) indexes with 
parallel docIDs. 

For example: use DeleteByQuery and feed it with Filter with set bits on docID 

----- Original Message ----
> From: Toke Eskildsen <>
> To: "" <>
> Sent: Fri, 22 October, 2010 14:27:45
> Subject: Re: Polymorphic Index
> On Fri, 2010-10-22 at 11:23 +0200, eks dev wrote:
> > Both of these  solutions are just  better way to do it wrong :) The real 
> >  is definitely somewhere around ParallelReader usage.
> The problem with  parallel is with updates of documents. The IndexWriter
> takes terms and  queries for deletions and that does not work with the
> parallel approach as  there must be separate IndexWriters for each index.
> There will be no indexed  UIDs in the searcher-oriented index, so there
> is no way to perform the  deletions.
> > Ideally, one should be able to say by opening index which  parts of index he 
> > going to be using. One way to do it is to to  create Parallel Indexes, 
> > part is fully functional and already  there. 
> That is correct. If IndexWriter accepted docIDs for deletions,  the
> parallel approach would work (get the docID by searching the  parallel
> index, then use it for deletions in both indexes). Unfortunately it  does
> not so you'll need to tweak the IndexWriter. I don't know how hard  that
> is.
> > Anyone using ParallelReader, any tips on creating  parallel indexes?
> I would suggest that you make sure that you can solve  the delete-problem
> first, before you start creating parallel  indexes.
> ---------------------------------------------------------------------
> To  unsubscribe, e-mail:
> For  additional commands, e-mail:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message