Ha. Cool! Nice to meet. I suggested to use this reader to some customers, but they were using Solr or Elasticsearch and it's not easy to implement it there. And they didn't want to pay the expensive Uwe. 😜
How do you handle deletes. Because the main issue with those readers is that you can't update documents without also updating the main reader (although it's a fake update). If this is used, have you thought of a SynchronizedMergePolicy that just applies the same merges in the secondary index? Uwe Am 2. Dezember 2023 10:27:20 MEZ schrieb Dawid Weiss <dawid.we...@gmail.com>: >> ParallelReader is also seldomly used, maybe we should remove support at >> some point. I don't know anybody using it, because it is very complicated >> to maintain consistent indexes. It only works with stable merge policies. >> > >You do know somebody - you know me. We're using it extensively - the >scenario is for storing data derived from the main document in a separate >index, merging this data dynamically. The data can then be reindexed/ >modified independently. Yes, we do use stable merge policies. > >Dawid -- Uwe Schindler Achterdiek 19, 28357 Bremen https://www.thetaphi.de
