Date 8

2017.01.05 - 번역 - Numeric and Date Ranges in Elasticsearch: Just Another Brick in the Wall ...

Like this post? Love numbers and Elasticsearch? I’ll be at Elastic{ON} to meet with attendees face to face and answer your questions. Consider attending the event. Hope to see you there.Imagine being able index your calendar to quickly find all events whose time range conflicts with a proposed event. Or creating a global television guide to find all shows, movies, sports, or broadcasts that are ..

Blog 2019.01.07

5. Tune for search speed

Give memory to the filesystem cache Elasticsearch heavily relies on the filesystem cache in order to make search fast. In general, you should make sure that at least half the available memory goes to the filesystem cache so that Elasticsearch can keep hot regions of the index in physical memory.Elasticsearch는 search 속도를 빠르게 하기 위해, filesystem cache에 많이 의존한다. 일반적으로, Elasticsearch가 index 중 많이 사용하는 ..

v2.0-04. Mapping changes

A number of changes have been made to mappings to remove ambiguity and to ensure that conflicting mappings cannot be created.모호함을 제거하고, mapping의 충돌이 일어나지 않도록 하기 위해, mapping에 많은 변경이 있었다.One major change is that dynamically added fields must have their mapping confirmed by the master node before indexing continues. This is to avoid a problem where different shards in the same index dynamically add..

v2.0-07. Search changes

Partial fieldseditPartial fields have been removed in favor of source filtering.source filtering를 위하여 partial field는 제거되었다.search_type=count deprecatededitThe count search type has been deprecated. All benefits from this search type can now be achieved by using the (default) query_then_fetch search type and setting size to 0.count search type은 deprecate되었다. 이 search type으로 얻을 수 있었던 것은 이제 (기본적으로)..

v2.0-08. Aggregation changes

Min doc count defaults to zeroeditBoth the histogram and date_histogram aggregations now have a default min_doc_count of 0instead of 1.histogram 과 date_histogram aggregation 둘 모두는 min_doc_count 의 기본값으로 1 대신에 0 을 가진다.Timezone for date fieldeditSpecifying the time_zone parameter in queries or aggregations on fields of type date must now be either an ISO 8601 UTC offset, or a timezone id. For examp..

1-06. Mapping and Analysis

While playing around with the data in our index, we notice something odd. Something seems to be broken: we have 12 tweets in our indices, and only one of them contains the date 2014-09-15, but have a look at the total hits for the following queries:index에 있는 데이터를 살펴보다 보면, 이상한 점을 발견할 수 있다. 뭔가 깨진 것 같다. index에는 12개의 tweet이 있다. 그 중의 단 하나만 2014-09-15 를 포함하고 있다. 그런데 아래 query의 total hits를 보면GET /_searc..

1-10-09. Customizing Dynamic Mapping

If you know that you are going to be adding new fields on the fly, you probably want to leave dynamic mapping enabled. At times, though, the dynamic mapping "rules" can be a bit blunt. Fortunately, there are settings that you can use to customize these rules to better suit your data.새로운 field를 추가하려는 것을, 지금 알고 있다면, dynamic mapping을 비활성화하고 싶을 것이다. 때때로, 동적 mapping "규칙" 은 조금 무딜 수 있다. 다행히도, 데이터에 더 적합..

2-1-4. Ranges

When dealing with numbers in this chapter, we have so far searched for only exact numbers. In practice, filtering on ranges is often more useful. For example, you might want to find all products with a price greater than $20 and less than $40.이 장에서 number를 다룰 때, 지금까지는 정확한 수만을 검색했었다. 실제로는, 범위를 filtering하는 것이 때때로 더 유용하다. 예를 들어, 가격이 $20보다 크고 $40보다 작은 모든 상품을 찾아보자.In SQL terms, a range can be express..