Skip to content

SOLR-16390: Migrate list cluster nodes API to JAX-RS - #4865

Open
iprithv wants to merge 5 commits into
apache:mainfrom
iprithv:SOLR-16390-list-cluster-nodes
Open

SOLR-16390: Migrate list cluster nodes API to JAX-RS#4865
iprithv wants to merge 5 commits into
apache:mainfrom
iprithv:SOLR-16390-list-cluster-nodes

Conversation

@iprithv

@iprithv iprithv commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

https://issues.apache.org/jira/browse/SOLR-16390

Converts GET /api/cluster/nodes from the homegrown @EndPoint wrapper to JAX-RS, matching ClusterProperty / ListCollections.

  • JAX-RS interface ListClusterNodesApi and typed ListClusterNodesResponse already existed in solr/api
  • ListClusterNodes owns the live-node listing
  • Path and response key nodes are unchanged
  • SolrJ ClusterApi.ListClusterNodes
  • HTTP coverage in SolrCloud (lists live nodes) and standalone (400 when not SolrCloud)

@github-actions github-actions Bot added documentation Improvements or additions to documentation tests cat:api labels Sep 2, 2026
Signed-off-by: prithvi <prithvisivasankar@gmail.com>
@iprithv
iprithv force-pushed the SOLR-16390-list-cluster-nodes branch from cc54ba4 to 26b2e1d Compare September 2, 2026 14:55
@epugh epugh self-assigned this Sep 2, 2026
@epugh
epugh requested a review from gerlowskija September 2, 2026 15:32
@epugh

epugh commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Looks like the old ClusterAPI.getNodes() @EndPoint never got removed — it's still shadowing the new JAX-RS class for real traffic. Confirmed by running ListClusterNodesStandaloneTest, which fails (500 instead of 400) because the request never reaches ListClusterNodes. #4866 removed the analogous legacy methods for the command-status migration — same fix needed here for getNodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

admin-ui cat:api documentation Improvements or additions to documentation tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants