lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-8029) Modernize and standardize Solr APIs
Date Thu, 26 May 2016 14:38:13 GMT

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

Noble Paul edited comment on SOLR-8029 at 5/26/16 2:37 PM:
-----------------------------------------------------------

Thanks Cassandra

bq.Schema endpoints don't seem to include GET methods for fields, copyfields or dynamic fields.
 

Right , those specs are not included in the output. Will add them

bq.Replacements for the Blob Store API and the ConfigSets API are not included?

Not yet, I'm planning to add them to the v2 path as is. 
I need to write the spec for them




was (Author: noble.paul):
Thanks Cassandra

bq.Schema endpoints don't seem to include GET methods for fields, copyfields or dynamic fields.
 

Right , those specs are not included in the output. Will add them

bq.Replacements for the Blob Store API and the ConfigSets API are not included?

Not yet, I'm planning to add them to the v2 path as is. 



> 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
>              Labels: API, EaseOfUse
>             Fix For: 6.0
>
>         Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch
>
>
> 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 | 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


Mime
View raw message