Hi, Steven,

Although it's true that you would need to re-index your content for the
frequently updated fields, you would *not* need to re-index the
large/stale content index, as long as you keep constant the number of
documents and the order in which you index them.


This seems good but too strict and not practical for me. And I doubt
it's useful for any real practice also...

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"?

--
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, Steven Rowe <[EMAIL PROTECTED]> wrote:
Hi Chris,

Chris Lu wrote:
> Hi, Steven,
>
> Thanks for the instant reply! But let's see the warning in the
> ParallelReader javadoc:
> "It is up to you to make sure all indexes are created and modified
> the same way. For example, if you add documents to one index, you need
> to add the same documents in the same order to the other indexes.
> Failure to do so will result in undefined behavior."
>
> To follow the warning, I need to index the all content again. So
> basically it defeats my original purpose to keep two indexes: to save
> the indexing for the large/stale content.

Although it's true that you would need to re-index your content for the
frequently updated fields, you would *not* need to re-index the
large/stale content index, as long as you keep constant the number of
documents and the order in which you index them.

Steve

---------------------------------------------------------------------
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]

Reply via email to