But you can do something very similar and very quickly using a unique ID (not the Lucene ID) that's shared across the indexes (assuming I'm reading your issue correctly). Then use TermDocs/TermEnum and create your filters that way.
I predict endless problems with user (programmer) errors if Lucene allowed one to specify the (lucene) document ID. I suspect it just ain't going to happen since nobody has yet made a case for why this would be enough better than the current system to be worth the hassle. Best Erick On 12/19/06, Antonio Bruno <[EMAIL PROTECTED]> wrote:
To use but directly the docId would render efficient and fastest the searches much. Thoughts to the possibility of being able to apply a first CachingWrapperFilter F1 on an index and a second CachingWrapperFilter F2 on an other index and after to make (F1 AND F2) and to even extract the info of interest only from an index. It would be most powerful… Could be made the moment one what of this type? Antonio Bruno (T&S - Cosenza Italy) __________________________________________________ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it
