One thing that makes the cutover easier would be using aliases feature in
your Solr cloud.
You have old data in something like collection_2022 and the alias is just
collection. Then new index format with new Solr version goes to
collection_2023 assuming you have the spare space and CPU. Do some te
Shawn,
On 8/25/23 13:04, Shawn Heisey wrote:
On 8/25/23 10:44, Shawn Heisey wrote:
On 8/25/23 10:21, Christopher Schultz wrote:
I believe we have only used Solr 7 and above. Is there a way to
confirm without actually /trying/ it?
There is this very cool endpoint shared by Rahul that I did no
Tim,
On 8/25/23 08:23, Tim Funk wrote:
This had been my normal upgrade path now for the major upgrades:
0) Optimistically assume you have all the original data for re-inserts
Check! Everything going into the index also goes into tables in our
RDBMS. Solr is just there to make things go *much
Greetings fellow forum members,
Our team is currently working with Solr 8.11 in cloud mode to power our
search system, built using Java Spring at the application layer. We're
facing a challenge in maintaining up-to-date pricing information for our
ecommerce platform, which experiences frequent dat
Hi Solr Users,
Is there a feature to request main ranker results in case of a reranker
request failure due to incorrect request params, for example, incase of LTR
as reranker, if the model is not found, the complete request fails with
"model not found" error, instead of that is it possible to
On 8/25/23 10:44, Shawn Heisey wrote:
On 8/25/23 10:21, Christopher Schultz wrote:
I believe we have only used Solr 7 and above. Is there a way to
confirm without actually /trying/ it?
There is this very cool endpoint shared by Rahul that I did not know about:
I can confirm that running this
On 8/25/23 10:21, Christopher Schultz wrote:
I believe we have only used Solr 7 and above. Is there a way to confirm
without actually /trying/ it?
There is this very cool endpoint shared by Rahul that I did not know about:
localhost:8983/solr//admin/segments
Look for "createdVersionMajor" in
On 8/25/23 02:19, Tim Pfeifer (ext) wrote:
Firstly, I appreciate the Lucidworks resource shared earlier. However, it
doesn't cover the CVEs related to jackson-databind that I've outlined below.
These vulnerabilities are a point of concern for our security department.
In version 8.11.2, Solr i
Shawn,
On 8/24/23 16:38, Shawn Heisey wrote:
On 8/24/23 14:02, Christopher Schultz wrote:
I'm preparing to upgrade a standalone Solr server from 7.7.3 -> 8.11.2
and I wanted to confirm a few things.
First, I'm assuming that the new server will be willing to open and
modify the existing index
Just my 2 cent:, I have always used solr clients as singletons. You have to
instantiate them only once and reuse them forever.
On Fri, 25 Aug 2023 at 15:35, Tim Funk wrote:
> Update - It looks like the ThreadLocal leak is different and unrelated to
> creating / closing a new Http2SolrClient eve
Update - It looks like the ThreadLocal leak is different and unrelated to
creating / closing a new Http2SolrClient every request. Even using a
shared
Http2SolrClient for my webapp - I noticed the same issue in a QA
environment
of leaking ThreadLocals. Falling back to HttpSolrClient optimistically
This had been my normal upgrade path now for the major upgrades:
0) Optimistically assume you have all the original data for re-inserts
1) Copy your config to fresh blank instance
2) Verify your solrconfig.xml has an update to date
3) Fix other solrconfig.xml deprecations such as replacing such a
Hello All,
Firstly, I appreciate the Lucidworks resource shared earlier. However, it
doesn't cover the CVEs related to jackson-databind that I've outlined below.
These vulnerabilities are a point of concern for our security department.
CVE Concerns
I've compiled a list of CVEs related to jac
13 matches
Mail list logo
