[
https://issues.apache.org/jira/browse/SOLR-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16120783#comment-16120783
]
Jan Høydahl commented on SOLR-11183:
------------------------------------
My concern is that if we advertise /v2 as a major feature and the new "default"
from 7.0, then it gets harder and harder to change the URL since so many users
out there will have adopted /v2, the same with all docs, blogs etc.
If it is very hard to change the /v2 end-point name, then the design probably
has too much redundant hard coding? I find 44 occurrences of {{/v2}} and 20
occurrences of {{____v2}} in the code base, including comments and docs.
> 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
> Fix For: 7.1
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
