serhiy-bzhezytskyy opened a new pull request, #5122: URL: https://github.com/apache/solr/pull/5122
https://issues.apache.org/jira/browse/SOLR-18498 # Description The examples on the CoreAdmin page start the node with `bin/solr start -DconfigSetBaseDir=./server/solr/configsets -e techproducts`. Since Solr 10 that starts SolrCloud, where both the V1 and the V2 `CREATE` example fail with `coreNodeName missing`. The default `solr.xml` has no `configSetBaseDir` property, so the `-D` has no effect. # Solution The page starts the example with `--user-managed` and drops the `-D`; the `sample_techproducts_configs` configset is found in the default `configsets` directory. Written with Claude Code. # Tests On a node started with the new command, the V1 and V2 `CREATE` examples both return status 0, with or without the `-D`. `buildLocalAntoraSite` and `checkSiteLinks` pass. # Checklist - [x] I have reviewed the guidelines for [How to Contribute](https://github.com/apache/solr/blob/main/CONTRIBUTING.md) and my code conforms to the standards described there to the best of my ability. - [x] I have created a Jira issue and added the issue ID to my pull request title. - [x] I have given Solr maintainers [access](https://help.github.com/en/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork) to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation) - [x] I have developed this patch against the `main` branch. - [ ] I have run `./gradlew check`. - [ ] I have added tests for my changes. - [x] I have added documentation for the [Reference Guide](https://github.com/apache/solr/tree/main/solr/solr-ref-guide) - [ ] I have added a [changelog entry](https://github.com/apache/solr/blob/main/dev-docs/changelog.adoc) for my change -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
