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

David Smiley edited comment on SOLR-18450 at 10/20/26 8:09 AM:
---------------------------------------------------------------

[~ab] I see you backported 2 of the 3 issues here to 10_1.  The 3rd had 
important documentation for users as to the impact of this change.  Given the 
feature freeze was in place for a while, I don't think it makes sense to bring 
a very noticeable change (for V2 API users) like this into 10_1.  Please revert 
them.


was (Author: dsmiley):
@sigram I see you backported 2 of the 3 issues here to 10_1.  The 3rd had 
important documentation for users as to the impact of this change.  Given the 
feature freeze was in place for a while, I don't think it makes sense to bring 
a very noticeable change (for V2 API users) like this into 10_1.  Please revert 
them.

> Evolve v2 /api/cluster to be limited to limited to collection state and live 
> under V2 /api/collections?detailed=true
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-18450
>                 URL: https://issues.apache.org/jira/browse/SOLR-18450
>             Project: Solr
>          Issue Type: Sub-task
>          Components: v2 API
>            Reporter: Eric Pugh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 10.2
>
>         Attachments: SOLR-18450-node-status.patch
>
>          Time Spent: 7.5h
>  Remaining Estimate: 0h
>
> We have learned that we need the /api/cluster to return everything, if you 
> request at this level for Solr Operator and some others.   See this email 
> thread for the analysis: 
> [https://lists.apache.org/thread/vk7wd4chz2hf489pg1svdnj80h60rdkr.]
>  
> What we have learned is that the current V2 cluster status, not only is not 
> jax-rs, but it alos includes things we don't need.  For example, liveNodes, 
> clusterProperties, roles, aliases (of course we don't need includeAll!)   And 
> maybe even "_route_"?
>  
> So we would like to migrate /api/cluster to the modern V2 jax rs with strong 
> typing, with the tree of collections and shards in one big response.  But 
> remove all the other cruft that is duplicating data that other APIs provide.
>  
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to