I copy here this information as well.
Another detail that comes to my mind is that the SolrServer used to process
the request is *CloudSolrServer.*
I will check the implementation of the method.
2013/12/14 Alessandro Benedetti
> Thank you Raymond,
> so what's wrong in the code ?
> Who is respon
Thank you Raymond,
so what's wrong in the code ?
Who is responsible to decide if that params will go to the Header or in the
body?
Which is the "library I am using" you quoted ?
I am using that objects from SolrJ API library.
2013/12/13 Raymond Wiker
> I think you're wrong about this; both the
I think you're wrong about this; both the "literal.*"parameters and the file
will be sent as part of the body, as "multipart/form-data". It is possible that
whatever library you're using are placing the "literal.*" parameters in the
url, but that is by no means necessary (or even a good idea).
I think you're wrong about this; both the "literal.*"parameters and the file
will be sent as part of the body, as "multipart/form-data". It is possible that
whatever library you're using are placing the "literal.*" parameters in the
url, but that is by no means necessary (or even a good idea).
Hi guys,
I was working with the ContentStreamUpdateRequest in solr 4.5 to send to
Solr a document with a set of metaData through an HTTP POST request.
Following the tutorial is easy to structure the request :
*contentStreamUpdateRequest.setParam("literal.field1","value1");*
*contentStreamUpdate
