[
https://issues.apache.org/jira/browse/SOLR-18450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124443#comment-18124443
]
ASF subversion and git services commented on SOLR-18450:
--------------------------------------------------------
Commit b3345a97b0d59820bf75fefc2a0fcdfaf8268d90 in solr's branch
refs/heads/main from Serhiy Bzhezytskyy
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=b3345a97b0d ]
SOLR-18450: Use /api/collections in test_auth.bats (#5055)
> 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
> Attachments: SOLR-18450-node-status.patch
>
> Time Spent: 5h 10m
> 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]
