[
https://issues.apache.org/jira/browse/SOLR-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626897#comment-17626897
]
Sanjay Dutt commented on SOLR-15751:
------------------------------------
[~gerlowskija] So I was reading both ClusterStatus.java and ColStatus.java.
*Existing*
||API||Class||
|/v2/collections/<collName> |ClusterStatus.java|
|solr/admin/collections?action=CLUSTERSTATUS|ClusterStatus.java|
|solr/admin/collections?action=COLSTATUS|ColStatus.java|
Do we have any discussion regarding this change that we should add more info
(detailed index information) to the CLUSTERSTATUS API?
Because as I am reading the code, Yes the `ColStatus.java` and `ClusterStatus`
does have some similar code? But in my opinion, both have different usage.
So I think we should create v2 endpoints for 'COLSTATUS' something like
'v2/collection/<collname>/colstatus' rather than changing the
ClusterStatus.java. Thoughts on that? **
> Create a v2 equivalent for 'COLSTATUS'
> --------------------------------------
>
> Key: SOLR-15751
> URL: https://issues.apache.org/jira/browse/SOLR-15751
> Project: Solr
> Issue Type: Sub-task
> Components: v2 API
> Reporter: Jason Gerlowski
> Priority: Major
> Labels: V2, newdev
>
> Solr's 'COLSTATUS' command under the v1 \{{/solr/admin/collections}} endpoint
> has no full v2 equivalent. The \{{/v2/collections/<collName>}} API has
> similar (identical?) output as a vanilla COLSTATUS request, but COLSTATUS can
> also return detailed index information that \{{/v2/collections/<collName>}}
> cannot expose. We should add parameters to this v2 API to expose similar data
> to achieve parity with the v1 COLSTATUS API.
--
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
