[
https://issues.apache.org/jira/browse/SOLR-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ishan Chattopadhyaya updated SOLR-11183:
----------------------------------------
Attachment: SOLR-11183.patch
Updating [~noble.paul]'s latest patch to replace some more documentation
references.
I'm planning to commit this to the 7.0 branch in an hour or so, unless there
are any objections. I'll am okay with reverting this after the commit if there
are any objections.
> 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
>
> Attachments: SOLR-11183.patch, SOLR-11183.patch, SOLR-11183.patch,
> SOLR-11183.patch
>
>
> 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
