Hi Adrien,
Yes, that can be done. I just wanted to make sure my understanding is
correct and that's how the future API is going to look like before we do
this refactoring. Thank you.
--
Regards,
Alex
On Tue, Jul 18, 2023 at 3:26 PM Adrien Grand wrote:
> Hi Alexander,
>
> You mentioned that yo
Hi Alexander,
You mentioned that your current implementation relies on a single
IndexSearcher. Could you have two instead? One that configures an executor
for long running queries and another one that doesn't?
For reference, IndexSearchers are cheap to create, it would be ok to create
one per que
Hi everyone,
We performed testing of the concurrent rewrite for knn vector queries in
Lucene 9.7 and the results look great, we see up to x9 improvement on large
datasets.
Our current implementation for intra-query concurrency relies on a single
IndexSearcher per index which is always configured w
Sorry for duplicating the question.
On Tue, Jul 18, 2023 at 19:09 Amitesh Kumar wrote:
> I am facing a requirement change to get % sign retained in searches. e.g.
>
> Sample search docs:
> 1. Number of boys 50
> 2. My score was 50%
> 3. 40-50% for pass score
>
> Search query: 50%
> Expected resu
I am facing a requirement change to get % sign retained in searches. e.g.
Sample search docs:
1. Number of boys 50
2. My score was 50%
3. 40-50% for pass score
Search query: 50%
Expected results: Doc-2, Doc-3 i.e.
My score was
1. 50%
2. 40-50% for pass score
Actual result: All 3 documents (becau
