to be
returned?
Thank you,
Marc Davenport
Hello,
I'm finally migrating Lucene from 8.11.2 to 9.10.0 as our overall build can
now support Java 11. The quick first step of renaming packages and
importing the new libraries has gone well. I'm even seeing a nice
performance bump in our average query time. I am however seeing a dramatic
ild but it's a
> logarithmic bisection and you'd know for sure where the problem is.
>
> D.
>
> On Thu, Apr 18, 2024 at 11:16 PM Marc Davenport
> wrote:
>
> > Hi Adrien et al,
> > I've been doing some investigation today and it looks like whatever the
> > change is, it ha
egression. It would
> be interesting to look at a profile.
>
> On Wed, Apr 17, 2024 at 9:32 PM Marc Davenport
> wrote:
>
> > Hello,
> > I'm finally migrating Lucene from 8.11.2 to 9.10.0 as our overall build
> can
> > now support Java 11. The quick first step o
and match the previous behavior.
Marc
On Fri, Apr 19, 2024 at 4:39 PM Marc Davenport
wrote:
> Hello,
> Thanks for the leads. I haven't yet gone as far as doing a git bisect, but
> I have found that the big jump in time is in the call to
> facetsConfig.build(taxonomyWriter, doc); I
n use your own cache implementation,
> similar
> > to what you can see in tests - TestDirectoryTaxonomyWriter.java
> > or TestConcurrentFacetedIndexing.java. This would
> > allow you to plug in the previous implementation (or something even more
> > fine-tuned to your need
Hello,
I'm exploring some personalization to our sort orders. If I have an
original query q which is mostly just a set of term filters, and I want to
sort those by distance between some float vector on the document and a
supplied user vector. I only see one way to do this. I would create a new
