1.6.8 Content Streams

1. Content Streams

When the requesthandlers request is accessed based on the URL path, Solrqueryrequest contains the requested parameters and also contains a list of contentstreams (containing the bulk data).

1.1 Stream Sources

Currently requesthandlers can get content stream in a variety of ways.

• For multiple file uploads, each file is passed as a stream.
• For a POST request, the content type cannot be application/x-www-form-urlencoded. The body of the post is passed as a stream. The body of the entire post is parsed as a parameter and is included in the SOLR parameter.
• The contents of the Stream.body parameter are passed as stream.
• If the remote stream pass is turned on, the URL request can be invoked. The contents of each Stream.url and Stream.file parameter are crawled and passed as a stream.

By default, Curl sends a application/x-www-form-urlencoded header. If you want to test a solrcontentheader stream. You need to set the stream type with "-H".

1.2 remotestreaming

The remote pass stream lets you send the contents of a URL as a stream to solrrequesthandler. For some security reasons, remote streaming is off in Solrconfig.xml.

Note: If streaming is turned on, This allows a request to be sent to any URL or local file. If the warehouse (dump) is turned on, it will allow any system to access files on your system.

<!-- Make sure your system have authentication before enabling remote streaming!  - <  enableremotestreaming= "true"  multipartuploadlimitinkb= "2048"  />

1.3 Debugging Requests

<name= "/debug/dump"  class= "SOLR. Dumprequesthandler "/>

This handle uses the specified writer type wt. SIMPLE output solrqueryrequest content. This is a very useful tool in helping to understand what kind of streams is available for solrqueryrequest.

1.6.8 Content Streams