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

Cao Manh Dat edited comment on SOLR-10715 at 6/6/17 11:37 AM:
--------------------------------------------------------------

[~janhoy] {{_introspect}} is documentation page for correspond command. But 
{{/v2}} is a welcome page more than a command. So I don't think we need 
{{/v2/_introspect}} support. 
BTW: Error message will be nicely written by SOLR-10406


was (Author: caomanhdat):
[~janhoy] {{_introspect}} is documentation page for correspond command {{/v2}} 
is a welcome page more than a command. So I don't think we need 
{{/v2/_introspect}} support. 
BTW: Error message will be nicely written by SOLR-10406

> /v2/ should not be an alias for /v2/collections
> -----------------------------------------------
>
>                 Key: SOLR-10715
>                 URL: https://issues.apache.org/jira/browse/SOLR-10715
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: v2 API
>    Affects Versions: 6.5
>            Reporter: Jan Høydahl
>
> Spinoff from SOLR-10711
> Currently {{/v2}} is [a hardcoded 
> alias|https://github.com/apache/lucene-solr/blob/9fa04ecc9521d4528dc61a2447a199d9ce56a86a/solr/core/src/java/org/apache/solr/api/V2HttpCall.java#L82-L87]
>  for {{/v2/collections}} (but similar aliasing is not done for _introspect.
> It would be more useful to reserve {{/v2}} as a generic entry-point that 
> works both in cloud and standalone mode. Perhaps instead that endpoint should 
> report something similar as {{bin/solr status}}, i.e. version, node name, 
> cluster size (nodes) and status (red/green/yellow), number of collections, 
> number of local cores and a simple help text for how to use the API?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to