[
https://issues.apache.org/jira/browse/SOLR-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14480874#comment-14480874
]
Noble Paul commented on SOLR-7054:
----------------------------------
The objective is to have a single endpoint that normal REST users will
understand. Once we define the behavior the we can think of implementing them
as we wish
> a pure REST interface for all operations in Solr
> ------------------------------------------------
>
> Key: SOLR-7054
> URL: https://issues.apache.org/jira/browse/SOLR-7054
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
>
> It would be a single handler say {{/docs}}
> GET would do a query
> GET /docs is equivalent to /select/q=*:*
> GET /docs?q=a:b will be equivalent to /select?q=a:b
> GET /docs/docId will be equivalent to /select?q=id:docId
> PUT/POST /docs is equivalent to /update and the default format for json would
> be that of /update/json/docs
> DELETE /docs/id will do a delete by id
> DELETE /docs?q=x:val is delete by query
> We can think of implementing this as a new {{RequestHandler}} without
> changing anything in Solr. Itcan be configured as follows
> {code:xml}
> <requestHandler name="/docs" class="RestRequestHandler"
> get="/select" <!--This will just use the /select handler to handle http GET
> -->
> post="/update/json/docs" <!-- All POST requests will use the handloer
> configured at /update/json/docs -->
> put="/update/json/docs" <!-- PUT requests will use same as POST -->
> delete="/update"/> <!-- DELETE requests will use /update as well -->
> {code}
>
>
--
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
