serhiy-bzhezytskyy opened a new pull request, #4993: URL: https://github.com/apache/solr/pull/4993
https://issues.apache.org/jira/browse/SOLR-18491 # Description Four Ref Guide pages show an API call only in its v1 form, although a working v2 endpoint exists for it. This adds the V1/V2 tabs used elsewhere in the guide. # Solution * `exporting-result-sets.adoc`: the three `/export` examples get a V2 tab (`/api/collections/collection_name/export` with the same parameters). Both tabs name the same index, so the placeholder `core_name` becomes `collection_name` in the V1 tab too. * `schemaless-mode.adoc`: the three `curl` calls for `/schema/fields` and `/schema/copyfields` sat inside sentences; each sentence is split around a V1/V2 tabs block. * `solr-in-docker.adoc`: creating a collection through the remote API gets a V2 tab (`POST /api/collections` with a JSON body). The page already creates `gettingstarted3` with the third way, so this fourth example now uses `gettingstarted4`. * `jwt-authentication-plugin.adoc`: the `curl` with the `Authorization` header gets a V2 tab (`/api/node/system`). # Tests `./gradlew :solr:solr-ref-guide:buildLocalAntoraSite :solr:solr-ref-guide:checkSiteLinks` passes with no warnings or errors. In the built HTML each new block has the same `tabs` / `tablist` / `tabpanel` structure as the existing V1/V2 tabs. Each V2 request returned 200 on a local Solr built from main. The `/export` examples used `techproducts` fields in place of the log fields, and the JWT request ran without the plugin configured, so it exercises the route and the header only. AI-assisted (Claude Sonnet 5). -- 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]
