[jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs

["Shawn Heisey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738705#comment-14738705 ] 

Shawn Heisey commented on SOLR-8029:
------------------------------------

I have no real wish to derail your plan, but I wondered about a possible wrinkle:  In order to have a /solr2 URL work, doesn't that require a completely separate context, and therefore a separate application from Jetty's point of view?  If this is true, are there any problems in getting the two to work together?  They would be in the same JVM, but for general security concerns I would hope that the servlet API keeps them pretty separate.

Something to think about ... I wonder if maybe paths under /CONTEXT/api (where CONTEXT is defined in the context fragment for the container and is normally "solr") would be a better way to separate this out.  At that point, you could put the new angular UI on /CONTEXT/ui.  Having separate and clear URLs for ui and api would make it a lot easier for a user to know that they can't put a ui URL into a program that expects to talk to the api.

> Modernize and standardize Solr APIs
> -----------------------------------
>
>                 Key: SOLR-8029
>                 URL: https://issues.apache.org/jira/browse/SOLR-8029
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 6.0
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>             Fix For: 6.0
>
>
> Solr APIs have organically evolved and they are sometimes inconsistent with each other or not in sync with the widely followed conventions of HTTP protocol. Trying to make incremental changes to make them modern is like applying band-aid. So, we have done a complete rethink of what the APIs should be. The most notable aspects of the API are as follows:
> The new set of APIs will be placed under a new path {{/solr2}}. The legacy APIs will continue to work under the {{/solr}} path as they used to and they will be eventually deprecated.
> There are 3 types of requests in the new API 
> * {{/solr2/<collection-name>/*}} : Operations on specific collections 
> * {{/solr2/_cluster/*}} : Cluster-wide operations which are not specific to any collections. 
> * {{/solr2/_node/*}} : Operations on the node receiving the request. This is the counter part of the core admin API
> This will be released as part of a major release. Check the link given below for the full specification.  Your comments are welcome
> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org