不爲也 比不能也

While Elasticsearch comes with many queries, you will use just a few frequently. We discuss them in much greater detail in Search in Depth but next we give you a quick introduction to the most important queries.Elasticsearch에는 많은 query가 있지만, 자주 사용하는 것은 소수일 것이다. Search in Depth에서, 훨씬 더 자세히 이야기할 것이다. 아래에서 가장 중요한 query들에 대해 빠르게 소개하겠다.match_all QueryeditThe match_all query simply matches all documen..

The multi_match query provides a convenient shorthand way of running the same query against multiple fields.multi_match query는, 여러 field에 동일한 query를 실행하는, 아주 편리한 query이다.There are several types of multi_match query, three of which just happen to coincide with the three scenarios that we listed in Know Your Data: best_fields, most_fields, and cross_fields.multi_match query는 여러 가지 형태가 있다. Know You..

Full-text search is a battle between recall—returning all the documents that are relevant—and precision—not returning irrelevant documents. The goal is to present the user with the most relevant documents on the first page of results.full-text 검색은 recall(적합한 document 모두를 반환하는)과 정확성(precision)(부적합한 document를 반환하지 않는)의 전쟁이다. 결과의 첫 번째 page에 가장 적합한 document를 사용자에게 제시하는 것이 목표이다.To improve recall, we ..

Now we come to a common pattern: cross-fields entity search. With entities like person, product, or address, the identifying information is spread across several fields. We may have a person indexed as follows:이제 일반적인 패턴(여러 field에 대한 항목 검색 - cross fields entity search)을 시작해 보자. 사람(person), 제품(product), 주소(address) 같은 항목의 식별 정보는, 여러 field에 걸쳐 저장한다. 특정인의 정보는 아래처럼 색인될 것이다.{ "firstname": "Peter", "l..

The custom _all approach is a good solution, as long as you thought about setting it up before you indexed your documents. However, Elasticsearch also provides a search-time solution to the problem: the multi_match query with type cross_fields. The cross_fields type takes a term-centric approach, quite different from the field-centric approach taken by best_fields and most_fields. It treats all ..

The final topic that we should touch on before leaving multifield queries is that of exact-value not_analyzed fields. It is not useful to mix not_analyzed fields with analyzed fields in multi_matchqueries.다중 field 검색을 마치기 전에, 다뤄야 할 마지막 주제는, exact-value not_analyzed field이다. multi_match query에서, not_analyzed field와 analyzed field를 섞는 것은 유용하지 않다.The reason for this can be demonstrated easily by lo..

The match query supports fuzzy matching out of the box:match query는 기본적으로 퍼지 일치를 지원한다.GET /my_index/my_type/_search { "query": { "match": { "text": { "query": "SURPRIZE ME!", "fuzziness": "AUTO", "operator": "and" } } } }The query string is first analyzed, to produce the terms [surprize, me], and then each term is fuzzified using the specified fuzziness.query string은, 단어 [surprise, me] 를 만들어내기 위..