Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9CDB518A7F for ; Tue, 3 Nov 2015 16:54:36 +0000 (UTC) Received: (qmail 65716 invoked by uid 500); 3 Nov 2015 16:54:28 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 65616 invoked by uid 500); 3 Nov 2015 16:54:28 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 65358 invoked by uid 99); 3 Nov 2015 16:54:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2015 16:54:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id F1F392C1F7D for ; Tue, 3 Nov 2015 16:54:27 +0000 (UTC) Date: Tue, 3 Nov 2015 16:54:27 +0000 (UTC) From: "Noble Paul (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-8029) Modernize and standardize Solr APIs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987600#comment-14987600 ] Noble Paul commented on SOLR-8029: ---------------------------------- The argument was that all operations fall under three categories * cluster specific * node specific * collection specific If a new resource comes up it has to be one of these so it will be a sub path under these > Modernize and standardize Solr APIs > ----------------------------------- > > Key: SOLR-8029 > URL: https://issues.apache.org/jira/browse/SOLR-8029 > Project: Solr > Issue Type: Improvement > Affects Versions: Trunk > Reporter: Noble Paul > Assignee: Noble Paul > Labels: API, EaseOfUse > Fix For: Trunk > > > 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//*}} : 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