Hello everyone,
I was wondering if we can have a 8.9.0 release. It has been more than 3
months since 8.8.0 was released.
8.9.0 doesn't need to be the last release in the 8.x series.
Thanks.
The Solr project is interested in consuming specific snapshots of Lucene
builds in order to pin the dependency temporarily until 9.0 is released.
By specific snapshots, I don't mean something that changes daily, I mean an
immutable versioned snapshot. Cassandra suggested that
Hello,
I have been recovering from Covid so this has been delayed.
Apologies for not being able to look into this. This is on my ToDo
list for this week.
On Thu, May 6, 2021 at 9:48 PM Walter Underwood wrote:
>
> How do we make progress on SOLR-15056?
>
> This is a simple fix:
>
> * Improve
How do we make progress on SOLR-15056?
This is a simple fix:
* Improve the name for an existing circuit breaker
* Add a new circuit breaker that does what the name for the first one suggested
* Make the documentation more accurate
I submitted a patch in mid-January. I resubmitted those as a PR
+1
On Thu, May 6, 2021 at 7:50 PM Mayya Sharipova
wrote:
> Hello everyone,
> I was wondering if we can have a 8.9.0 release. It has been more than 3
> months since 8.8.0 was released.
> 8.9.0 doesn't need to be the last release in the 8.x series.
>
> Thanks.
>
Understood, getting well is more important.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On May 6, 2021, at 9:23 AM, Atri Sharma wrote:
>
> Hello,
>
> I have been recovering from Covid so this has been delayed.
>
> Apologies for not being able to
Do we have a way to understand how BooleanQuery (and other composite
queries) are advancing their child queries? For example, a simple
conjunction of two queries advances the more restrictive (lower
cost()) query first, enabling the more costly query to skip over more
documents. But we may not be
Generally you go over the least frequent to most frequent required terms as
the pivot. As you get more and more complicated queries, the ordering of
the query results tends to dominate. This also means there are two types
of measurement. One for the running query and one for query + results in
We have something like that in Elasticsearch that wraps queries in order to
be able to report cost, matchCost and the number of calls to
nextDoc/advance/matches/score/advanceShallow/getMaxScore for every node in
the query tree.
It's not perfect as it needs to disable some optimizations in order
+1
Mayya, are you volunteering to be the release manager?
Le jeu. 6 mai 2021 à 18:06, Ishan Chattopadhyaya
a écrit :
> +1
>
> On Thu, May 6, 2021 at 7:50 PM Mayya Sharipova
> wrote:
>
>> Hello everyone,
>> I was wondering if we can have a 8.9.0 release. It has been more than 3
>> months since
Thanks Adrien, that is something like what I had in mind. If you are
able to share, that could be very helpful. And -- deleted docs is not
something I had considered, it's possibly a problem here. I'd have to
go check - I think these "filter" Queries were implemented in the
second part of the
11 matches
Mail list logo
