Elasticsearch in the word breaker component configuration

The first thing to make clear is that Elasticsearch is Lucene-based, and many of its basic components are provided by Apache Lucene, while ES provides a higher level of encapsulation and distribution enhancements and extensions.

So if you want to master the knowledge of ES in the word segmentation, we must first start from Lucene, otherwise it will only be confused, of course, most of US developers only focus on how to use, the bottom of the east, there is not too much time to delve into, this also sentient can original, encountered problems to explore, It is also not a way, if there is time, or suggest a look at the basic knowledge of lucene.

In Elasticsearch or SOLR, the configuration-based pluggable plug-in is provided, which is managed in a way that is flexible in the form of a composite configuration, in ES, an analysis collection
Can contain multiple analyzer, and an analyzer consists of a single tokenizer, 0 or more tokenfilter, and a tokenizer can contain 0 or more charfilter. The overall execution process is as follows:


650) this.width=650; "Src=" http://dl2.iteye.com/upload/attachment/0113/2519/ 6d5a46ad-568e-38b9-a3b0-bb56a0b47229.png "title=" click to view original size picture "class=" Magplus "width=" "height=" 383 "style=" border : 0px;font-size:14px;white-space:normal;background-color:rgb (255,255,255); Font-family:helvetica, Tahoma, Arial, sans-serif;line-height:25.1875px; "/>


A template in ES is configured as follows:

Java code 650) this.width=650; "class=" star "src=" Http://qindongliang.iteye.com/images/icon_star.png "alt=" Favorites Code "style= "border:0px;"/>

2. Index:

4. Analysis://An analysis can consist of multiple analyzer,tokenizer,filter,char_filter configurations

6. Analyzer://An analyzer can contain a tokenizer, multiple filter and Char_filter, Position_increment_gap is the distance from the query, the maximum allowable query, the default is 100

8. MyAnalyzer1:

10. Type:custom

12. Tokenizer:mytokenizer1

14. Filter: [MyTokenFilter1, MyTokenFilter2]

16. Char_filter: [my_html]

18. Position_increment_gap:

20. MyAnalyzer2:

22. Type:custom

24. Tokenizer:mytokenizer1

26. Filter: [MyTokenFilter1, MyTokenFilter2]

28. Char_filter: [my_html]

30. Position_increment_gap:

34. Tokenizer:

36. MyTokenizer1:

38. Type:standard

40. Max_token_length:

42. MyTokenizer2:

44. Type:keyword

46. Max_token_length:

48. Filter:

50. MyTokenFilter1:

52. Type:stop

54. Stopwords: [Stop1, Stop2, STOP3, STOP4]

56. MyTokenFilter2:

58. Type:length

60. Min: 0

62. Max:

64. Char_filter:

66. My_html:

68. Type:html_strip

70. Escaped_tags: [XXX, yyy]

72. Read_ahead: 1024x768

A more complete case of the word breaker configuration, as in the example above, almost all of the possible components are covered, and we in the actual application, we have to do is to choose the components we need to customize into a word breaker, and then we can use,
The above configuration, we need to configure in the Elasticsearch.yml file, globally valid, then we can reference and use it in a static mapping or dynamic mapping.
Reference Links:
Https://www.elastic.co/guide/en/elasticsearch/reference/2.1/analysis-custom-analyzer.html

This article is from the "7936494" blog, please be sure to keep this source http://7946494.blog.51cto.com/7936494/1716107

Elasticsearch in the word breaker component configuration