The purpose of this email thread is to initiate a discussion about upgrading
the minimum Java version (Could be same as Lucene minimum Java for main branch
i.e. 21) for the main branch. We seek to understand the community's major
concerns and gather their guidance on this matter.
Regards,Sanjay
Interestingly, yesterday at the Search "Bird of Feather' @ Community Over
Code, Bratislava I brought this up too. All of us present in the room had
the same opinion about the page that at this point it only creates
confusion and we should remove it. For folks using older Solr versions,
this might s
We've got this utility TimeOut that assists waiting for a condition to
hold in a limited period of time. As a generic utility, of course it
involves a sleep period. We use it in many places. IMO it's a sad
choice to use when it's possible to alternatively wait on a condition
that will wake up the
I used it back in the days when you could migrate from v3->4->5->6. It solved
the issue that Solr 6 could only read a Lucene 6 or Lucene 5 index, but after
the
sequence of upgrades you'd get there. I even wrote a wrapper to automate it all
at
https://github.com/cominvent/solr-tools/tree/master/up
I've fielded many questions on this from clients. Folks who have managed
databases expect to be able to upgrade the data serially across versions
and such, so these questions come up alot with organizations early in their
journey with search. Essentially, I tell them that it's a stop gap tool for
u
FWIW, in my experience I've never run this tool (nor colleagues) at
any stage in my career that I can remember. For one reason, all the
systems could re-index if they needed to.
It may be best to remove this information, as it could introduce more
confusion than it helps.
On Mon, Jun 3, 2024 at 1
Hey all,
I was poking around the ref-guide a bit recently and noticed our page
on the "IndexUpgraderTool" that Lucene produces. [1]
AFAICT, the page doesn't hint at when/why a user might want to use the
IndexUpgraderTool. Maybe at one point the tool might've been
preferred to loading the index i
Maybe.
Yeah the song is just meant to be funny.
The long / extremely short, limited value, overview of my view is that
pretty much every classical way you can share clusterstate with Zookeeper
is an Overseer design, at least how I defined or thought of an Overseer
before it had any implementation