Exactly. For the case in point that is the real, underlying subject of this
thread, the desire is to partially update an existing Solr document using
the output of SolrCell/Tika.
With true/pure REST, that should be the HTTP "PUT" verb. And the path would
indicate the collection and key value. Maybe something like:
PUT
http://localhost:8983/solr/collections/example/id/doc-23?format=SolrCell...
And to delete a doc:
DELETE http://localhost:8983/solr/collections/example/id/doc-23
And to add or completely replace a single doc:
POST
http://localhost:8983/solr/collections/example/id/doc-23?format=SolrCell...
or
POST
http://localhost:8983/solr/collections/example?format=SolrCell&id=doc-23
Not that I'm seriously suggesting that Solr should be changed in this way at
this stage. I'm simply indicating one place where a closer-to-pure REST API
would have made it more clear what the application developer's intentions
were - and maybe have completely avoided this entire thread.
-- Jack Krupansky
-----Original Message-----
From: Yonik Seeley
Sent: Sunday, June 16, 2013 6:41 PM
To: solr-user@lucene.apache.org
Subject: Re: Adding pdf/word file using JSON/XML
On Sun, Jun 16, 2013 at 6:05 PM, Jack Krupansky <j...@basetechnology.com>
wrote:
Except, that Solr's divergence from a true, pure REST API is certainly one
of the elements of its "badness".
Most complex systems seem to feel the need to diverge from pure REST
for the sake of being practical.
From that perspective "pure REST" can be a disadvantage. We need to
be more specific about the advantages/disadvantages of specific points
in an API.
-Yonik
http://lucidworks.com
