Patrick Zhai

> Thanks @zhaih! > > Do we think this might mean we can turn back on the rearrange step and use multiple threads to build the "for deterministic searching" index?...

Hi Shubham, thanks for taking this task, and sorry for reviewing it late, I think the PR is a little bit different than what I think it ideally should be....

Oh I suddenly realized we're allocating ids dynamically, so it is normal that they are different run by run

@rmuir I can work on it if you don't want to do it right now?

I think the overall process in my mind would be: 1. Identify all deletes and save them 2. Create a document selector which ignores all deletes in the original index...

I **think** this looks like a bug (but probably not hurting a lot? Because the segment is dropping anyway?) but I'm not 100% sure. @mikemccand do you have any ideas?

Hi @jpountz thank for taking a look! > We already have one class that wraps an IndexReader and an Executor: IndexSearcher. Should this new rewrite method take an IndexSearcher instead...

@jpountz You're right, our case is a bit complex since currently we're not even using Lucene's Query (but we're planning to in the future!) so I totally forgot the createWeight...

Yeah I already made this one only on Lucene 10, I'll make a 9x PR according to Adrien's suggestion, it sounds not too complicated. (Thanks Uwe as well, good to...

I tried created one but then realized it seems not working, because query rewriting are rewriting query from top of the tree to the bottom so once we delegate to...