SOLR Management Interface Detailed __SOLR

Original address: http://blog.csdn.net/zcl_love_wx/article/details/52092098

The SOLR server management interface allows you to view the system status, SOLR settings, Word detection, query indexing, core changes, view logs, etc. 1.Dashboard (dashboard)

When you visit HTTP://LOCALHOST:8080/SOLR, this main page appears to see the use of SOLR uptime, SOLR version, system memory, and virtual machine memory

2.Logging ( log)

Displays the exception or error that occurred with the SOLR run

3.Core admin (Core management)

Mainly add core (add cores), Unload (uninstall Core), Rename (rename core), Reload (Reload Core), Optimize (optimized index Library)
Add core is a core: a core.properties file is generated primarily in the Instancedir corresponding folder

Name: names to the core;
Instancedir: Consistent with the new core folder name we created in Solr_home when configuring SOLR to Tomcat;
DataDir: When the add core is confirmed, a folder named data is generated in the New_core directory
Config profile (solrconfig.xml) under the Conf config:new_core
Schema:new_core under the Conf schema file (schema.xml)

When the add core is confirmed, the data folder and the Core.properties file are generated under New_core. The contents of the Core.properties file are as follows:
4.Java Properties

to view information about Some of the properties that are related to Java 5. Core Selecter (core selector)

you need to add the core to the core admin to be able to have the option, here take the already added Ims_advertiser_core for example. 5.1 Overview (Overview)

Contains basic statistics such as the current number of documents, and instance information such as the current core configuration directory;
5.2 Analysis (analytical)

test participle effect , such as figure, we have the CompanyName field participle (as for which fields can be participle, depending on the schema.xml file configuration of the field when the type is configured for the type of word breaker Text_ik)

<field name= "CompanyName" type= "Text_ik" indexed= "false" stored= "true" multivalued= "false"/>
//Text_ here IK is the value of the following Name property
    
    
     
     1
     
     2
    
    
    
    
     
     
    
    
    
    
     
     1
     
     2
    
    

 <!--Configure the IK word breaker start--> <fieldtype name= "Text_ik" class= "SOLR. TextField "positionincrementgap=" > <analyzer type= "index" > <tokenizer class= "ORG.WLTEA.ANALYZER.L" Ucene. Iktokenizerfactory "usesmart=" false "Ismaxwordlength=" false "/> <filter class=" SOLR. Lowercasefilterfactory "/> </analyzer> <analyzer type=" Query "> <tokenizer class=" org.wlt Ea.analyzer.lucene.IKTokenizerFactory "usesmart=" false "Ismaxwordlength=" false "/> <filter class=" SOLR.
     
     Lowercasefilterfactory "/> </analyzer> </fieldType> 1 2 3
    
    
    
    
     
     
    
    
    
    
     
     4 5 6 7 8 9 10 11 12
     
     1 2 3 4 5
    
     6 7 8 9 10 11 12

The highlight here is the background color is gray
5.3 dataimport (import data from database)

The prerequisite is that the relevant configuration is already configured, see also: SOLR import data from the database

comman Options: full_import: Full import; Delta_import: incremental import.
The so-called delta-import is primarily for importing fields that have been added or modified in databases (and possibly files, and so on). The main principle is the utilization of the Dataimport.properties file generated under solr.home\conf every time we import it, this file contains information about the most recent import. This document is as follows:
#Tue June 10:15:50 CST 2016
Advertiser.last_index_time=2016-07-19 10:15:49
Last_index_time=2016-07-19 10:15:49
In fact, Last_index_time is the time of the most recent index (Full-import or Delta-import).
By comparing this time with the timestamp column in our database table, we can draw what is later modified or added.

Verbose:
Clean: Delete Previous indexes before indexing starts building, default to True
Commit: Whether to commit after the index completes. The default is True
Optimize: Whether the index is optimized after the index completes. The default is True
Debug: Run in debug mode, suitable for interactive development (interactive development mode).
Note that if you run in debug mode, the default is not automatically submitted, please add the parameter "Commit=true"

Entity:entity is the label under document (Data-config.xml). Use this parameter to optionally perform one or more entity. Using multiple entity parameters enables multiple entity to run concurrently. If you do not select this parameter, all will be run.
Start,rows:
Custom Parameters:
excute: Perform import.
Refresh Status: Before you can see the data change after refreshing, if the data is still 0 after the refresh, the description is not imported. 5.4 Documents

Documents (index document) index related operations, such as: Add, modify, delete , etc., for example we want to add an index (CompanyName) method:
A. First, under the Schema.xml configuration file in Solr's D:\solr_home\mycore1\conf, add the relevant field fields

<field name= "CompanyName" type= "Text_ik" indexed= "false" stored= "true" multivalued= "false"/>
    
    
     
     1
    
    
    
    
     
     
    
    
    
    
     
     1
    
    

Otherwise, the following error occurs:

status:error Error:bad Request Error: {"Responseheader": {"Status
    
    
     
     ":", "Qtime": 1}, "error": {"MSG": "Error: [doc=126] Unknown field ' CompanyName '", "Code": 400}}
     
     1 2 3 4 5 6 7 8
    
    
    
    
     
     
    
    
    
    
     
     9 10 11 12 13
     
     1 2 3 4 5 6 7 8 9 10 

B. On the following page, select/update, document Format Select JSON, and submit submission. So the index is added. modifications are/update, as with additions, and are deleted as/delete .
After the success, we went to query data to find the data we just added.

Request-handler (QT): Action to be performed (Update\delete)
Document type: Type, with JSON, XML, and other formats
Document (s): Content, manually written content.
Commit Within:
Overwrite: True to overwrite the previous value if the ID is repeated, or false to indicate that if the ID repeats does not overwrite the previous value.
Boost: It seems to be a version, no use 5.5 files folder

Solr_home under the core of the Conf under the related files, you can click to view the contents.
5.6 Query (Query page), the results of the query to display which field, you have to configure the Schema.xml file configuration field when the stored property to true.

Querying indexed documents, including whether they exist, whether they are sorted correctly, and so on

When you enter the page, when you click Execute query directly, the data is returned on the right side:

Request-handler (QT):
Q: The query string (required). : means query all; Keyword: East look at the key word "East" query
FQ: Filter query filters queries. Use filter query to make full use of the filter query Cache to improve retrieval performance. function: In the Q query conforms to the result in the same time is FQ the query conforms to (similar intersection), for example: q=mm&fq=date_time:[20081001 to 20091031], find the keyword mm, and date_ Time is between 20081001 and 20091031.
SortSort The format is as follows: The field name is sorted, such as Advertiserid DESC indicates that the query results are sorted in descending order by ID field.
start,rows: Indicates that the results are displayed from the first few data and how many are displayed.
FL: Field list. Specifies which fields the query results return. Multiple times are separated by space "" or comma, "". When not specified, the default is all returned.
DF: Default field defaults to the query field, which is generally specified by default.
Raw Query Parameters:
WT: Write type. Specifies the query output format, which is commonly used in JSON format and XML format. The query output format is defined in Solrconfig.xml: XML, JSON, Python, Ruby, PHP, Phps, Custom.
Indent: Whether the returned results are indented, closed by default, with Indent=true | On open, the general debugging Json,php,phps,ruby output is necessary to use this parameter.
Debugquery: Sets whether the return result displays debug information.
Dismax:
Edismax:
HL: High light highlight. Hl=true indicates that highlighting is enabled
HL.FL: A list of fields separated by spaces or commas (specify highlighted fields). To enable the highlight feature of a field, you must ensure that the field is stored in the schema. If the parameter is not given, the default field is highlighted standard handler will use the DF parameter and the Dismax field with the QF parameter. You can use the asterisk to easily highlight all the fields. If you use wildcard characters, consider enabling the Hl.requiredfieldmatch option.
Hl.simple.pre：
Hl.requirefieldmatch: If set to true, it is highlighted unless the query result for the field is not empty. Its default value is False, which means it might match a field but highlight a different field. If HL.FL uses wildcard characters, then the parameter should be enabled. Still, if your query is the all field (possibly using the Copy-field Directive), set it to false so that the search results indicate which field the query text was not found
Hl.usephrasehighlighter: If a query contains a phrase (quote box), then it is guaranteed that the phrase must be exactly matched to be highlighted.
Hl.highlightmultiterm: If you use wildcards and fuzzy searches, you will be sure that the term that match the wildcard characters will be highlighted. The default is False, and hl.usephrasehighlighter to true.
Facet: Group statistics, while searching for keywords, can be grouped and counted according to facet fields.
Facet.query: Facet query uses syntax similar to filter query to provide a more flexible Facet. You can filter any field by using the Facet.query parameter.
Facet.field: Fields that require grouping statistics can be multiple.
Facet.prefix: The prefix that represents the value of the Facet field. such as Facet.field=cpu&facet.prefix=intel, then the CPU field for the facet query, the return of the CPU is the beginning of Intel, AMD the beginning of the CPU model will not be counted.
Spatial:
spellcheck: Spell check.