Apache Solr open-source search software
SOLR-18450: Document which major version the /api/collections details lands in (#5064)
Eric Pugh900e45b3c065
diff --git a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adocindex d8450340a57..2221fc7020b 100644--- a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc+++ b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-10.adoc@@ -99,6 +99,18 @@ Former users of `solr.api.v2.enabled` looking to upgrade to Solr 10.1 or newer sUsers who deploy a proxy in front of Solr should also review this setup to ensure that it allows access to the v2 API root path, `/api`.+=== V2 API++In Solr 10.2 `GET /api/collections?detailed=true` returns the collections, shards, and replicas tree under `collectionsDetail`.+It does not include `live_nodes`, the alias map, or cluster properties.+Use `GET /api/cluster/nodes`, `GET /api/aliases`, and `GET /api/cluster/properties` for those.++There is no `includeAll` parameter.+A request with no other parameters returns every collection.+`collection`, `shard`, and `_route_` narrow which part of the tree is returned.++The v1 `CLUSTERSTATUS` command is unchanged, and `includeAll` still defaults to true.+=== JWT AuthenticationThe `blockUnknown` setting in the JWT Authentication plugin now defaults to `true`, meaning requests without a valid JWT token are blocked by default.diff --git a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-11.adoc b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-11.adocindex 0372e4b820b..ac2de0f8137 100644--- a/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-11.adoc+++ b/solr/solr-ref-guide/modules/upgrade-notes/pages/major-changes-in-solr-11.adoc@@ -41,15 +41,3 @@ bin/solr start -Dsolr.node.roles=data:on,overseer:preferredA node started this way asks the Overseer to re-run its node prioritization, so a preferred node takes over without waiting for the current Overseer to restart.Note that node roles are fixed for the lifetime of a node: unlike `ADDROLE`, they cannot be changed on a running node.--=== V2 collections tree--`GET /api/collections?detailed=true` returns the collections, shards, and replicas tree under `collectionsDetail`.-It does not include `live_nodes`, the alias map, or cluster properties.-Use `GET /api/cluster/nodes`, `GET /api/aliases`, and `GET /api/cluster/properties` for those.--There is no `includeAll` parameter.-A request with no other parameters returns every collection.-`collection`, `shard`, and `_route_` narrow which part of the tree is returned.--The v1 `CLUSTERSTATUS` command is unchanged, and `includeAll` still defaults to true.