Re: Custom SliceExecutor and slices computation in IndexSearcher

a GitHub issue[1] and PR[2] to share the changes and will look forward to the feedback. [1]: https://github.com/apache/lucene/issues/12347 [2]: https://github.com/apache/lucene/pull/12348 Thanks, Sorabh On Sat, May 27, 2023 at 1:09 AM SorabhApache wrote: > Hi Luca, > Thanks for the sugg

Re: Custom SliceExecutor and slices computation in IndexSearcher

do you think? I personally prefer this > option over adding a function argument to the existing searcher > constructor, or making the slices non-final which affects the inter-segment > concurrency design (slices should not be mutable?). > > Cheers > Luca > > On Fri, May 1

Re: Custom SliceExecutor and slices computation in IndexSearcher

e task creation, and the coordination of their execution could be > moved to the SliceExecutor too. > > Cheers > Luca > > On Fri, May 19, 2023, 03:27 SorabhApache wrote: > >> Hi All, >> >> For concurrent segment search, lucene uses the *slices* method to >> c

Custom SliceExecutor and slices computation in IndexSearcher

Hi All, For concurrent segment search, lucene uses the *slices* method to compute the number of work units which can be processed concurrently. a) It calculates *slices* in the constructor of *IndexSearcher*

Re: Request for suggestion/pointers

Gentle reminder for below email. Thanks, Sorabh On Sun, May 17, 2020 at 5:53 PM SorabhApache wrote: > Hi, > I am new to the community and is interested in learning about Lucene > architecture and capabilities. Before diving into the code directly I am > looking for some suggestion

Request for suggestion/pointers

Hi, I am new to the community and is interested in learning about Lucene architecture and capabilities. Before diving into the code directly I am looking for some suggestion/pointers on how to start about it. Probably something which can give a high level overview and talk about few core concepts i