不爲也 比不能也

string fields replaced by text/keyword fieldseditThe string field datatype has been replaced by the text field for full text analyzed content, and the keyword field for not-analyzed exact string values. For backwards compatibility purposes, during the 5.x series:string field datatype이 full text analyzed 내용에 대해서는 text field로, not-analyzed exact string 값에 대해서는 keyword field로 변경되었다. 이전 version과의 호환..

Percolator is near-real timeeditPreviously percolators were activated in real-time, i.e. as soon as they were indexed. Now, changes to the percolate query are visible in near-real time, as soon as the index has been refreshed. This change was required because, in indices created from 5.0 onwards, the terms used in a percolator query are automatically indexed to allow for more efficient query sel..

The completion suggester has undergone a complete rewrite. This means that the syntax and data structure for fields of type completion have changed, as have the syntax and response of completion suggester requests. See completion suggester for details. 자동완성(completion suggester)은 완전히 다시 작성되었다. 즉, completion type의 field에 대한 구문 및 데이터 구조가 변경되었고, 이에 따라 completion suggester request에 구문 및 response가 변경..

Closing / deleting indices while running snapshoteditIn previous versions of Elasticsearch, closing or deleting an index during a full snapshot would make the snapshot fail. In 5.0, the close/delete index request will fail instead. The behavior for partial snapshots remains unchanged: Closing or deleting an index during a partial snapshot is still possible. The snapshot result is then marked as ..

?refresh no longer supports truthy and falsy valueseditThe ?refresh request parameter used to accept any value other than false, 0, off, and no to mean "make the changes from this request visible for search immediately." Now it only accepts ?refresh and ?refresh=true to mean that. You can set it to ?refresh=false and the request will take no refresh-related action. The same is true if you leave ..

From Elasticsearch 5.0 on all settings are validated before they are applied. Node level and default index level settings are validated on node startup, dynamic cluster and index setting are validated before they are updated/added to the cluster state.Elasticsearch 5.0 부터 모든 설정의 적용되기 전에 유효성을 검사한다. node level과 index level 설정은 시작 시에 유효성이 검사되고, 동적 cluster 및 index 설정은 cluster state에 업데이트/추가되기 전에 유효성..

Primary shard allocationeditPreviously, primary shards were only assigned if a quorum of shard copies were found (configurable using index.recovery.initial_shards, now deprecated). In case where a primary had only a single replica, quorum was defined to be a single shard. This meant that any shard copy of an index with replication factor 1 could become primary, even it was a stale copy of the da..

Compressed HTTP requests are always acceptededitBefore 5.0, Elasticsearch accepted compressed HTTP requests only if the setting http.compressedwas set to true. Elasticsearch accepts compressed requests now but will continue to send compressed responses only if http.compressed is set to true.5.0 이전에, Elasticsearch는 http.compressed 설정이 true 로 설정된 경우에만 압축된 HTTP request를 허용했다. 이제, Elasticsearch는 압축된..

Strict REST query string parameter parsingeditPrevious versions of Elasticsearch ignored unrecognized URL query string parameters. This means that extraneous parameters or parameters containing typographical errors would be silently accepted by Elasticsearch. This is dangerous from an end-user perspective because it means a submitted request will silently execute not as intended. This leniency h..

Use Accept header for specifying response media typeeditPrevious versions of Elasticsearch accepted the Content-type header field for controlling the media type of the response in the cat API. This is in opposition to the HTTP spec which specifies the Accept header field for this purpose. Elasticsearch now uses the Accept header field and support for using the Content-Type header field for this ..