11.05.2016 Views

Apache Solr Reference Guide Covering Apache Solr 6.0

21SiXmO

21SiXmO

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

langid.fallbackFields string none no If no language is detected that meets the<br />

langid.threshold score, or if the<br />

detected language is not on the langid<br />

.whitelist, this field specifies<br />

language codes to be used as fallback<br />

values. If no appropriate fallback<br />

languages are found, <strong>Solr</strong> will use the<br />

language code specified in langid.fal<br />

lback.<br />

langid.fallback string none no Specifies a language code to use if no<br />

language is detected or specified in lan<br />

gid.fallbackFields.<br />

langid.map.lcmap string determined by<br />

langid.lcmap<br />

no<br />

A space-separated list specifying colon<br />

delimited language code mappings to<br />

use when mapping field names. For<br />

example, you might use this to make<br />

Chinese, Japanese, and Korean<br />

language fields use a common *_cjk su<br />

ffix, and map both American and British<br />

English fields to a single *_en by using<br />

langid.map.lcmap=ja:cjk zh:cjk<br />

ko:cjk en_GB:en en_US:en.<br />

langid.map.pattern<br />

langid.map.replace<br />

Java<br />

regular<br />

expression<br />

Java<br />

replace<br />

none no By default, fields are mapped as<br />

_. To change this<br />

pattern, you can specify a Java regular<br />

expression in this parameter.<br />

none no By default, fields are mapped as<br />

_. To change this<br />

pattern, you can specify a Java replace<br />

in this parameter.<br />

langid.enforceSchema Boolean true no If false, the langid processor does not<br />

validate field names against your<br />

schema. This may be useful if you plan<br />

to rename or delete fields later in the<br />

UpdateChain.<br />

Content Streams<br />

When <strong>Solr</strong> RequestHandlers are accessed using path based URLs, the <strong>Solr</strong>QueryRequest object containing<br />

the parameters of the request may also contain a list of ContentStreams containing bulk data for the request.<br />

(The name <strong>Solr</strong>QueryRequest is a bit misleading: it is involved in all requests, regardless of whether it is a query<br />

request or an update request.)<br />

Stream Sources<br />

Currently RequestHandlers can get content streams in a variety of ways:<br />

For multipart file uploads, each file is passed as a stream.<br />

For POST requests where the content-type is not application/x-www-form-urlencoded, the raw<br />

POST body is passed as a stream. The full POST body is parsed as parameters and included in the <strong>Solr</strong><br />

<strong>Apache</strong> <strong>Solr</strong> <strong>Reference</strong> <strong>Guide</strong> <strong>6.0</strong><br />

235

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!