That would definitely help. Create a JIRA issue, then post your findings
after y'all have tried it out!
- Houston
On Wed, Oct 18, 2023 at 12:35 PM Tomasz Elendt
wrote:
> Of that helps I can build a custom image myself, upgrade a few clusters in
> my company and report back if there are any issu
Of that helps I can build a custom image myself, upgrade a few clusters in
my company and report back if there are any issues.
(Of course our deployment might not necessarily cover all edge cases.)
On Wed, Oct 18, 2023, 18:25 Houston Putman wrote:
> Might be a good thing to do for Solr 9.5.
>
>
Might be a good thing to do for Solr 9.5.
We hit some issues when moving 9.0 to JDK 17, which caused some trouble
and weren't particularly easy to fix without causing some compatibility
issues.
However, we are better equipped now to do quick fixes in the dockerfile
that don't require a bug-fix rel
I noticed that JDK 21 LTS was released some time ago. Is there any reason why
official docker images still use JDK 17?
I'm asking because I know there are some preview JDK features that Lucene
utilizes and Solr enables them when it detects a newer version (e.g.
SOLR-16500).
Does it make sense
I like this initiative and I love the fact we have a volunteer helping on
this, is it clear what are the next steps concretely?
Should we summarise them to have then the relevant actors to act?
I'm a bit busy after the conference (and another coming) but I can try to
help if needed.
Cheers
---
I believe its still useful for TLOG replicas as well. When they gain
leadership, and they replay the TLOG which could have the same issues that
non leader NRT replicas have.
- Houston
On Wed, Oct 18, 2023 at 8:26 AM David Smiley
wrote:
> Thank you both. It helps to know that "_version"_ is for
Sounds good Alejandro. You are defining the protocol (with collaborative
input). We have freedom to pretty much do as we feel is best. It's not a
voted artifact the project/PMC produces (which would have rules /
ceremony). If you want to "publish" the newsletter at a certain date &
time that is
Created a Jira, and sent in a PR to LTR
https://issues.apache.org/jira/browse/SOLR-17037
https://github.com/apache/solr/pull/2022
🙏
On Tue, Oct 17, 2023 at 4:45 PM Doug Turnbull
wrote:
> My google-fu got better -- FWIW This looks like an issue fixed in the
> normal rerank query code, but not i
Thank you both. It helps to know that "_version"_ is for, I would say
succinctly, "NRT replication". I mean; that deserves to be said internally
in some places!
Might it be advantageous to imagine it being optional for non-NRT
replicas? I'm not sure if it saves anything or reduces complexity any
