On 6/14/2022 10:22 AM, Christopher Schultz wrote:
Does that mean I need to:
1. delete *:*
2. optimize
3. re-index everything
Is #2 something available via the SolrJ client, or do I have to issue
a REST call for that?
This code should delete everything, commit, and optimize, all with a
singl
Any help why it might be failing with 401 or what can I try ?
On Thu, Jun 9, 2022 at 5:13 PM Susheel Kumar wrote:
> This is the Solr setup using Solr operator with 8.11.1. I have posted on
> Solr operator channel as well but checking here as well as Http2SolrClient
> and CloudHttp2SolrClient sh
Shawn,
On 6/13/22 21:01, Shawn Heisey wrote:
On 6/13/2022 1:19 PM, Christopher Schultz wrote:
Okay. So if I do what I initially proposed:
1. delete *:*
2. re-index everything
If you do this but do not optimize the index (which will happen
practically instantaneously because the index will c
Alias switching is a very good option for cloud users, and one of the
benefits of using cloud. OP is on "user managed" (also previously known as
"standalone" and then briefly as "legacy mode") so this is not available.
Order of preference:
1) build 100% new into new index (much better than the res
In my experience, you need to index to a new collection, then use the
alias command to point the connection endpoint to the new collection.
Not sure how this works in non-cloud mode.
We've tried reindexing to an existing collection, but, the created
LUCENE version stamp doesn't get updated, an
