You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Anakhe Ajayi (Jira)" <ji...@apache.org> on 2022/12/12 09:28:00 UTC
[jira] [Commented] (SOLR-15751) Create a v2 equivalent for 'COLSTATUS'
[ https://issues.apache.org/jira/browse/SOLR-15751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17645997#comment-17645997 ]
Anakhe Ajayi commented on SOLR-15751:
-------------------------------------
[~gerlowskija] still waiting for a response on this -
{panel:title=My title}
For clarification purposes, should we create a ColStatusAPI class with an endpoint /v2/collections/<collName> or simply add the missing parameters to the existing CollectionStatusAPI?
{panel}
> 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-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org