[
https://issues.apache.org/jira/browse/SOLR-8045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924720#comment-15924720
]
Hoss Man commented on SOLR-8045:
--------------------------------
bq. Huh? ... what you mean by "v2 api is not yet released" ... there seems to
be plenty of v2 API related code released in 6.4.0 ??
whoops ... my mistake. I must not have been been looking at the correct branch.
the crux of my question is still about the effective default behavior of this
{{registerPath}} option ... because i see Dat's commit changing _existing_
tests & configs to use {{/solr} instead of {{/}} -- but it's not clear to be
that the _default_ *effective* value (of {{registerPath}} when unspecified by a
user) has been changed to {{/solr}} ... or if the default effective value is
impacted by this issue at all.
----
Or to put it in a (broader) nutshell: are we 100% certain existing 6.4 users
who upgrade their solr instances to branch_6x, w/o making any config changes,
are unaffected by this change?
> Deploy V2 API at /v2 instead of /solr/v2
> ----------------------------------------
>
> Key: SOLR-8045
> URL: https://issues.apache.org/jira/browse/SOLR-8045
> Project: Solr
> Issue Type: Wish
> Reporter: Noble Paul
> Assignee: Cao Manh Dat
> Priority: Blocker
> Fix For: 6.5
>
> Attachments: SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch,
> SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch, SOLR-8045.patch
>
>
> This does not mean that the path to access Solr will be changed. All paths
> will remain as is and would behave exactly the same
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
