不爲也 比不能也

This section discusses the changes that you need to be aware of when migrating your application from one version of Elasticsearch to another.여기에서는 application을 Elasticsearch 다른 version으로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.As a general rule:일반적으로Migration between major versions — e.g. 1.x to 2.x — requires a full cluster restart.major version간(예: 1.x 에서 2.x 으로)의 migration은 full cluster restart이 ..

SettingseditThe setting bootstrap.mlockall has been renamed to bootstrap.memory_lock. Future versions of Elasticsearch will refuse to start if bootstrap.mlockall is set. You can switch to the new setting now.bootstrap.mlockall 설정은 bootstrap.memory_lock 으로 이름이 변경되었다. Elasticsearch 향후 버전에서는 bootstrap.mlockall 설정되면 시작되지 않는다. 이제 새로운 설정으로 변경할 수 있다.

The optimize_bbox parameter for geo_distance and geo_distance_range queries has been deprecated when querying indexes created after 2.1.geo_distance 와 geo_distance_range query의 optimize_bbox 매개변수는 2.1 이후에 생성된 index를 query하는 경우 deprecate되었다.

Prior to 2.4, validation was not performed upon creation of an index template. Rather, the index template was validated upon index creation after all matching templates were fully merged.2.4 이전에서는, index template 생성시에 유효성 검증가 수행되지 않았다. 오히려, index template은 모든 일치하는 template이 완전히 병합된 후 index 생성시에 유효성이 검증되었다.Each index template must now be independently valid prior to merging. This means, for examp..

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

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.2.여기에서는 application을 Elasticsearch 2.2 로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.Geo Point TypeeditThe geo_point format has been changed to reduce index size and the time required to both index and query geo point data. To make these performance improvements possible both doc_values and..

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.1.여기에서는 application을 Elasticsearch 2.1 로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.Search changesUpdate changesIndex APIsRemoved features

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

Updates now detect_noop by defaulteditWe’ve switched the default value of the detect_noop option from false to true. This means that Elasticsearch will ignore updates that don’t change source unless you explicitly set "detect_noop": false. detect_noop was always computationally cheap compared to the expense of the update which can be thought of as a delete operation followed by an index operatio..

Optimize APIeditThe Optimize API has been deprecated, all new optimize actions should use the new Force Merge API.optimize API는 deprecate되었다. 모든 최적화 작업은 새로운 Force Merge API를 사용해야 한다.Queue size statseditThe value for the queue_size in nodes info/stats was sometimes shown as "1k" instead of 1000. These values are always shown as an integer now.node info/stats에서 queue_size 에 대한 값은 가끔씩 1000 이 아닌 "1k..