[ 
https://issues.apache.org/jira/browse/SOLR-15748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873227#comment-17873227
 ] 

David Smiley commented on SOLR-15748:
-------------------------------------

I would argue we didn't need this.  The information (e.g. aliases, or the 
status of one collection, live nodes) should be made available via V2 but we 
don't need a macro API to return a bunch of these things at once, which is what 
CLUSTERSTATUS is.  I suspect CLUSTERSTATUS may have been one of the original 
SolrCloud level APIs so it became somewhat of a kitchen sink of all things 
about the state/status.  In hindsight, I don't agree with it.  It ends up 
blowing up in size for clients that only need a subset of it, leading to 
decomposing it.  

> Create v2 equivalent of v1 'CLUSTERSTATUS' (or document alternatives)
> ---------------------------------------------------------------------
>
>                 Key: SOLR-15748
>                 URL: https://issues.apache.org/jira/browse/SOLR-15748
>             Project: Solr
>          Issue Type: Sub-task
>          Components: v2 API
>    Affects Versions: 9.1
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>              Labels: V2
>             Fix For: main (10.0), 9.2
>
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> Solr's 'CLUSTERSTATUS' command under the v1 {{/solr/admin/collections}} 
> endpoint has no v2 equivalent. This should be remedied to inch v2 closer to 
> parity with v1 in preparation for eventual v1 deprecation.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to