[SOLR-8029] Modernize and standardize Solr APIs

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.0
• Fix Version/s: 6.5, 7.0
• Labels: API EaseOfUse
• Assignee: Noble Paul
• Reporter: Noble Paul
• Created: 10/Sep/15 12:40
• Updated: 07/Aug/17 11:41
• Resolved: 10/Apr/17 03:27

Description

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 4 types of requests in the new API

• /v2/<collection-name>/* : Hit a collection directly or manage collections/shards/replicas
• /v2/<core>/* : Hit a core directly or manage cores
• /v2/cluster/* : Operations on cluster not pertaining to any collection or core. e.g: security, overseer ops etc

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

Issue Links

• incorporates: SOLR-5606 REST based Collections API
• is duplicated by: SOLR-1523 Destructive Solr operations accept HTTP GET requests
• is duplicated by: SOLR-5606 REST based Collections API
• is related to: SOLR-10432 V2 API follow up items
• relates to: SOLR-11183 Prefix V2 APIs with /api