[
https://issues.apache.org/jira/browse/SOLR-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116643#comment-16116643
]
Cassandra Targett commented on SOLR-11183:
------------------------------------------
I propose making this not a blocker for 7.0.
I don't see any reason why it wouldn't be possible to add an {{/api}} prefix as
an _alias_ for {{/v2}} at any time in a 7.x release as long as it's
back-compatible. Assuming that's the case, I don't think we need to hold up 7.0
for this.
> why call the API end point /v2 will there ever be a /v3
> -------------------------------------------------------
>
> Key: SOLR-11183
> URL: https://issues.apache.org/jira/browse/SOLR-11183
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.0
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Blocker
> Fix For: 7.0
>
>
> The mail thread
> http://lucene.472066.n3.nabble.com/v2-API-will-there-ever-be-a-v3-td4340901.html
> it makes sense to prefix v2 APIs at {{/api}} intsead of {{/v2}} if we never
> plan to have a {{/v3}}
> In principle, it makes total sense
> The challenge is that it takes a while to change the code and tests to make
> to work. Should this be a blocker and should we hold up the release
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
