epotyom commented on issue #9721:
URL: https://github.com/apache/lucene/issues/9721#issuecomment-2006430761

   Thanks @jpountz  for [bringing this up as a feature for Lucene 
10](https://lists.apache.org/list.html?d...@lucene.apache.org). It would be 
great to have if we can build it!
   
   A few of us in Amazon Product Search (+cc @stefanvodita , @slow-J) had been 
looking into it out of curiosity. We discussed implementing Cloneable for 
Scorer/BulkScorer as [previously 
suggested](https://github.com/apache/lucene/issues/9721#issuecomment-1223928468),
 but it looks like even implementing it just for the TermQuery scorer requires 
significant code changes, as there are quite a few dependencies that have to be 
Cloneable too. Maybe there is a hybrid approach? For example, when concurrent 
segment search is being initialized, it can try calling clone() for 
Scorer/BulkScorer, but if it throws CloneNotSupportedException, we fall back to 
creating a new Scorer/BulkScorer instance? Then we can implement the clone 
method only for scorers that are expensive to  initialize, e.g. range query 
scorers mentioned in the comments above.
   
   This approach still takes a lot of up-front effort. I’m curious if anyone 
has better ideas. The original patch seems to have been lost; it would have 
been really useful to have. Tagging @atris on the off-chance that he still has 
the patch or remembers what the implementation looked like.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to