[
https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430026#comment-15430026
]
Noble Paul commented on SOLR-8029:
----------------------------------
Thanks [~arafalov] A lot of stuff that is there is the spec is not implemented
. The scope is vast. I strongly recommend you to take a look at the branch
{{v2api}}
bq.configset - Zookeeper only? What about for non SolrCloud installations
There is no concept of a configset outside of SolrCloud
bq.Non-distributed collection terminology - Is it still collection or core? Or
both
The core APIs will continue to exist. So , both
bq.What's SMILE? Takes a while to find reference to some binary JSON,
It is not added as a part of v2 API. It already exists
bq.HJSON or HOCON (misspelling or two different things?)
HJSON actually. We want to be as forgiving as possible
bq.Operations are specified using snake case using either a dash or underscore
- Who is making this choice? Are some operations defined one way and others the
other?
They already exist. It is not added i V2 API
bq./v2/admin was already discussed for static resources, the spec should be
updated if that's accepted as the solution
The spec is not a complete future plan. We have a lot of missing pieces. The
objective is to include as much as possible and make a first release
bq.Still talks about /solr/v2
It is {{/solr/v2}}
bq.Is Schema auto-generated from something or manually written?
It is manually written. it is a part of the source code. Please check the
{{apiv2}} branch
A lot of stuff do not yet support schema . As of now only coponents with end
points (request handlers ) do have schema
bq.Does the name parameter support the full Java regex or just star? If just
star, there is no point being 'flexible' about. But if it is full regex (e.g.
test[a-z][0-9]) , it is worth mentioning.
bq.config param - return all collections that use the specific ?collection?
It is the same as the {{LIST}} command as of . It neither supports wild card
nor regex. We would like to add support on both end points together
bq. With async, why are we making request to one endpoint but getting its
status from another.
Interesting. We should explore the semantics of supporting the same
bq.Is there no useful information to be returned when collection is created?
Like which nodes it ends up on?
The responses are same as they are in V1 . Yes , it returns the nodes
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
