Hi David,
I have two requests and wanted to know if you would be ok with both,
either, or neither of these. In case you are ok, I should be able to merge
these and cherry pick to 9_11 latest by Saturday :

1) Extrapolating on your idea of renaming the index upgrade Collections API
(in progress in https://issues.apache.org/jira/browse/SOLR-18190) to
UPGRADEINDEX, I thought it would be nice to have consistency and also
rename the existing CoreAdmin api to UPGRADEINDEX, especially since 9.11
will be the first public release. Fairly trivial change.

2) Although currently the API form of the functionality only exists at core
level, it is possible to achieve this even for a SolrCloud collection by
configuring the LatestVersionMergePolicy and reindexing the collection.
I would like to add a note in the documentation elaborating this.

Thanks,
Rahul

On Thu, Apr 30, 2026 at 7:22 PM Jan Høydahl <[email protected]> wrote:

> > I'm not sure how the script or my approach should be updated.
>
> Venv is a good practice. I think you just lacked updating your PATH to
> point to the venv?
> Perhaps we should document how to setup venv with e.g. pyenv?
>
> > Question:
> https://ci-builds.apache.org/job/Solr/job/Solr-Docker-Nightly-9.x/
> > description says Moved to github workflows:
> > https://github.com/apache/solr/actions/workflows/docker-nightly.yml but
> > that is only true for main, not 9x nor even 10x.  The GH screen shows
> this,
> > not to mention the workflow yml file isn't on branch_9x (I didn't check
> > 10x).
>
> It is correct that the workflow only triggers once a night and only on
> main.
> That is because that one workflow builds all variants, it uses 'matrix',
> as can
> be seen in
> https://github.com/apache/solr/blob/main/.github/workflows/docker-nightly.yml
> In total it builds 11 snapshot variants on various branches, jdk versions
> and slim/full.
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to