lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ishan Chattopadhyaya (JIRA)" <>
Subject [jira] [Updated] (SOLR-11183) why call the API end point /v2 will there ever be a /v3
Date Sun, 20 Aug 2017 04:23:01 GMT


Ishan Chattopadhyaya updated SOLR-11183:
    Attachment: SOLR-11183.patch

I agree with [~janhoy] and I think we should release 7.0 with /api endpoint to keep things
consistent going forward. Attaching a patch that points /api to /solr/__v2 (i.e. earlier only
/v2 pointed to /solr/__v2, now both do so); please review. Although I think this is a minimal
risk change (but very important to get in now), I leave it to [~anshumg]'s judgement, though,
for inclusion in 7.0.

> why call the API end point /v2 will there ever be a /v3
> -------------------------------------------------------
>                 Key: SOLR-11183
>                 URL:
>             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
> The mail thread
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message