Thanks Chris Hostetter!
More questions:
1. When I use setBoost for document in index C, will that be counted in?
2. Does index A allow any deletion at all? If index A has some
deletions, I suppose index C should also delete those after
optimizing? But which deletion takes precedence?
3. If index A use compound file format, I suppose index C should also
be the same. When optimizing during creating the compound file, the
ordering will not be changed?
I am also interested to know any real production usage of ParallelReader.
--
Chris Lu
-------------------------
Instant Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo: http://search.dbsight.com
Lucene Database Search in 3 minutes:
http://wiki.dbsight.com/index.php?title=Create_Lucene_Database_Search_in_3_minutes
On 3/26/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I think the better question could be, given a large/stale index A, a
: small/updated index B, and the B does not satisfy the requirement of
: ParallelReader. How can I create an index C that "add the same
: documents in the same order of index A"?
1) optimize A so it has a single segment with no gaps in doc ids.
2) iterate over the docs in A, looking at their "unique key" field
-- FieldCache should be handy for this.
2.1) For each uniqueKey in A pull the corrisponding data out of B and
add the doc to C
...the key here being that B need not be a lucene index, just something
that provides fast lookup by your unique Key (liek a database perhaps)
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
