Introduction to schema. xml configuration of SOLR

Source: Internet
Author: User

The configuration of Schema. XML is as follows:

The following are common elements:

<Field name = "weight" type = "float" indexed = "true" stored = "true"/>

<Dynamicfield name = "* _ I" type = "int" indexed = "true" stored = "true"/>
<Dynamicfield name = "* _ is" type = "int" indexed = "true" stored = "true" multivalued = "true"/>

<Copyfield source = "cat" DEST = "text"/>

 

Reference: http://wiki.apache.org/solr/

The XML format is described as follows:

The schema. xml file contains all of the details about which fields your documents can contain, and how those fields shocould be dealt with when adding documents to the index, or when querying those fields.

This schema. the XML file contains all the details, including the fields that can be contained in multiple documents, how these fields are processed when multiple documents are added to the index, or when these fields are queried.

Analysis for multiterm queries can be separately specified, see: multiterm query analysis, which handles automatically lowercasing wildcard queries under most circumstances. solr3.6 solr4.0

Analysis of multiple queries can be specified separately. In most environments, lowercase letter wildcard queries can be automatically processed.

A sample SOLR schema. XML with detailed comments can be found in the source repository.

 

This example schema is the recommended starting point for users. It shoshould be kept correct and concise, usable out-of-the-box.
In this example, schema is an example of how to get started. It should be accurate, concise, available, and out-of-the-box.
For more information, on how to customize this file, please see http://wiki.apache.org/solr/SchemaXml
For more information, see:


Performance Note: This schema has des already optional features and shocould not be used for benchmarking. To improve performance one cocould

Note: This schema contains many optional features and should not be used as a benchmark example. To improve performance, we can do this:
-Set stored = "false" for all fields possible (esp large fields) when you only need to search on the field but don't need to return the original value.
-Set indexed = "false" if you don't need to search on the field, but only return the field as a result of searching on other indexed fields.
-Remove all unneeded copyfield statements
-For Best Index size and searching performance, set "Index" to false for all general text fields, use copyfield to copy them to the catchall "text" field, and use that for searching.
-For maximum indexing performance, use the concurrentupdatesolrserver Java client.
-Remember to run the JVM in server mode, and use a higher logging level that avoids logging every request

Introduction to schema. xml configuration of SOLR

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.