不爲也 比不能也

indices.fielddata.cache.expireeditThe experimental feature indices.fielddata.cache.expire has been removed. For indices that have this setting configured, this config will be ignored.실험적인 기능인 indices.fielddata.cache.expire 가 제거되었다. 이 설정을 가진 index의 경우 설정은 무시된다.Forbid changing of thread pool typeseditPreviously, thread pool types could be dynamically adjusted. The thread pool type effectively cont..

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.0.여기에서는 application을 Elasticsearch 2.0으로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.Indices created before 0.90editElasticsearch 2.0 can read indices created in version 0.90 and above. If any of your indices were created before 0.90 you will need to upgrade to the latest 1.x version of Ela..

Rivers have been removededitElasticsearch does not support rivers anymore. While we had first planned to keep them around to ease migration, keeping support for rivers proved to be challenging as it conflicted with other important changes that we wanted to bring to 2.0 like synchronous dynamic mappings updates, so we eventually decided to remove them entirely. See Deprecating Rivers for more bac..

Bind to localhosteditElasticsearch 2.x will only bind to localhost by default. It will try to bind to both 127.0.0.1 (IPv4) and [::1] (IPv6), but will work happily in environments where only IPv4 or IPv6 is available. This change prevents Elasticsearch from trying to connect to other nodes on your network unless you specifically tell it to do so. When moving to production you should configure th..

Previously, if the path.data setting listed multiple data paths, then a shard would be “striped” across all paths by writing a whole file to each path in turn (in accordance with the index.store.distributorsetting). The result was that files from a single segment in a shard could be spread across multiple disks, and the failure of any one disk could corrupt multiple shards.이전 버전에서는, path.data 설정..

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..

Explicit custom routingeditCustom routing values can no longer be extracted from the document body, but must be specified explicitly as part of the query string, or in the metadata line in the bulk API. See Type meta-fields for an example.사용자 정의 routing value는 더 이상 document body에서 추출할 수 없다. query string의 일부 또는 bulk API에서 metadata line에 명시적으로 지정하해야 한다. Type meta-fields에서 예제를 볼 수 있다.Routing hash f..

Queries and filters mergededitQueries and filters have been merged — all filter clauses are now query clauses. Instead, query clauses can now be used in query context or in filter context:query와 filter는 통합되었다. 모든 filter절은 이제 query절이다. 대신, 이제 query절은 query context 나 filter context 에서 사용된다.Query contextA query used in query context will calculate relevance scores and will not be cacheable. Query c..

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으로 얻을 수 있었던 것은 이제 (기본적으로)..

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..