不爲也 比不能也

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.3.여기에서는 application을 Elasticsearch 2.3 으로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.REST APIeditCORS support broken in 2.3.0 and 2.3.1editA change to the CORS implementation means that CORS support for pre-flight OPTIONS requests is broken in 2.3.0 and 2.3.1. This is fixed in 2.3.2.CORS 구..

search_type=scan deprecatededitThe scan search type has been deprecated. All benefits from this search type can now be achieved by doing a scroll request that sorts documents in _doc order, for instance:scan search type은 deprecate되었다. 이 search type으로 할 수 있는 것은 _doc 의 순서로 document를 정렬하는 scroll request로 가능하다. 예를 들어GET /my_index/_search?scroll=2m { "sort": [ "_doc" ] }Scroll requests sorted by _doc..

Besides the simple scalar datatypes that we have mentioned, JSON also has null values, arrays, and objects, all of which are supported by Elasticsearch.위에서 언급한 기본 데이터 type외에도, JSON은 null 값, 배열, 오브젝트도 가질 수 있다. Elasticsearch는 이들 모두를 지원한다.Multivalue FieldseditIt is quite possible that we want our tag field to contain more than one tag. Instead of a single string, we could index an array of tags:tag..

The previous two examples showed a single filter in use. In practice, you will probably need to filter on multiple values or fields. For example, how would you express this SQL in Elasticsearch?앞의 두 가지 예제는 단일 filter의 사용을 보여준다. 실제 상황에서는, 아마도 여러 값 또는 field를 filtering해야 할 것이다. 예를 들면, 아래의 SQL을 Elasticsearch에서는 어떻게 표현할까?SELECT product FROM products WHERE (price = 20 OR productID = "XHDK-A-1293-#fJ3")..

Just as we have seen a dozen times already, buckets can be nested in buckets for more-sophisticated behavior. For illustration, we will build an aggregation that shows the total sum of prices for all makes, listed by quarter. Let us also calculate the sum of prices per individual make per quarter, so we can see which car type is bringing in the most money to our business:이미 여러 번 본 것과 마찬가지로, 더 복잡..

Given the fact that creating, deleting, and updating a single document in Elasticsearch is atomic, it makes sense to store closely related entities within the same document. For instance, we could store an order and all of its order lines in one document, or we could store a blog post and all of its comments together, by passing an array of comments: Elasticsearch에서 단일 document를 생성, 수정, 삭제하는 것은 ..

Setting up a nested field is simple—where you would normally specify type object, make it type nested instead: nested field를 설정하는 것은 간단하다. 일반적으로 object type을 지정하는 곳에, type을 nested 로 대신 지정하면 된다.PUT /my_index { "mappings": { "blogpost": { "properties": { "comments": { "type": "nested", "properties": { "name": { "type": "string" }, "comment": { "type": "string" }, "age": { "type": "short" }, "stars..

Because nested objects are indexed as separate hidden documents, we can’t query them directly.Instead, we have to use the nested query to access them: nested object는 숨겨진 개별 document로 색인되기 때문에, 그들을 직접 query할 수 없다. 대신에, 그들을 nested query를 사용하여 액세스해야 한다.GET /my_index/blogpost/_search { "query": { "bool": { "must": [ { "match": { "title": "eggs" } }, { "nested": { "path": "comments", "query": { "bool..

It is possible to sort by the value of a nested field, even though the value exists in a separate nested document. To make the result more interesting, we will add another record: 값은 개별 nested document에 있지만, nested field의 값으로 정렬하는 것은 가능하다. 더 흥미로운 결과를 만들어내기 위하여, 또 다른 document를 추가해 보자.PUT /my_index/blogpost/2 { "title": "Investment secrets", "body": "What they don't tell you ...", "tags": [ "share..

In the same way as we need to use the special nested query to gain access to nested objects at search time, the dedicated nested aggregation allows us to aggregate fields in nested objects: 검색 시에, nested object에 액세스하기 위해, 특별히 nested query를 사용해야 하는 것과 동일한 방식으로, nested object에 있는 field를 aggregation하기 위한, 전용 nested aggregation이 있다.GET /my_index/blogpost/_search { "size" : 0, "aggs": { "comments": {..