[
https://issues.apache.org/jira/browse/SOLR-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16134475#comment-16134475
]
ASF subversion and git services commented on SOLR-11183:
--------------------------------------------------------
Commit 12bb39cee8c3f18914285fbdca08efa066ac4851 in lucene-solr's branch
refs/heads/branch_7x from [~ichattopadhyaya]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=12bb39c ]
SOLR-11183: V2 APIs are now available at /api endpoint
> Prefix V2 APIs with /api
> ------------------------
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
