不爲也 比不能也

Removal of throttle_time in the store statseditGiven that store throttling has been removed, the store stats do not report throttle_timeanymore.store throttling이 제거되었다는 것을 감안할 때, store stat은 throttle_time 을 더 이상 report하지 않는다.FS stats no longer reports if the disk spinseditElasticsearch has defaulted to assuming that it is running on SSDs since the 2.x series of Elasticsearch. As such, Elasticsea..

Remove support for elasticsearch.json and elasticsearch.yaml configuration fileeditThe configuration file found in the Elasticsearch config directory could previously have a .yml, .yamlor .json extension. Only elasticsearch.yml is now supported.Elasticsearch의 config directory에서 볼 수 있는 설정 file은 .yml, .yaml 또는 .json 이라는 확장자를 가질 수 있다. 이제 오직 elasticsearch.yml 만을 지원한다.Duplicate keys in configuration ..

Changes to querieseditThe collect_payloads parameter of the span_near query has been removed. Payloads will be loaded when needed.span_near query의 collect_payloads 매개변수는 제거되었다. 필요한 경우 payload가 load된다.Queries on boolean fields now strictly parse boolean-like values. This means only the strings "true" and "false" will be parsed into their boolean counterparts. Other strings will cause an error to ..

Groovy, JavaScript, and Python languages removededitThe Groovy, JavaScript, and Python scripting languages were deprecated in elasticsearch 5.0 and have now been removed. Use painless instead.elasticsearch 5.0 에서 Groovy, JavaScript, 그리고 Python scripting language가 deprecate되었고, 이제 제거되었다. 대신 painless를 사용하자.Native scripts removededitNative scripts have been removed. Instead, implement a ScriptEngin..

Unquoted JSONeditIn previous versions of Elasticsearch, JSON documents were allowed to contain unquoted field names. This feature was removed in the 5.x series, but a backwards-compatibility layer was added via the system property elasticsearch.json.allow_unquoted_field_names. This backwards-compatibility layer has been removed in Elasticsearch 6.0.0.Elasticsearch의 이전 버전에서는, JSON document에 인용되지 ..

size parametereditThe size parameter can no longer be explicitly set to -1. If all documents are required then the size parameter should not be set.size 매개 변수는 더 이상 명시적으로 -1 로 설정할 수 없다. 모든 document가 필요한 경우 size 매개 변수를 설정하지 않아야 한다.

Mapper attachments plugineditThe mapper attachments plugin has been deprecated in elasticsearch 5.0 and is now removed. You can use ingest attachment plugin instead.elasticsearch 5.0에서 mapper attachments plugin은 deprecate되었고, 이제 제거되었다. 대신, ingest attachment plugin 을 사용할 수 있다.S3 Repository plugineditThe bucket an s3 repository is configured with will no longer be created automatically. It must ex..

Deprecated percolator and mpercolate apis have been removededitInstead the percolate query should be used via either the search or msearch apis.대신 percolate query는 search나 msearch API를 통해 사용되어야 한다.The percolator.map_unmapped_fields_as_string setting has been deprecatededitThe percolator.map_unmapped_fields_as_text setting should be used instead.대신, percolator.map_unmapped_fields_as_text 설정이 사용되어..

Configuring custom user and group for package is no longer allowededitPreviously someone could configure the $ES_USER and $ES_GROUP variables to change which user and group Elasticsearch was run as. This is no longer possible, the DEB and RPM packages now exclusively use the user and group elasticsearch. If a custom user or group is needed then a provisioning system should use the tarball distri..

Coercion of boolean fieldseditPreviously, Elasticsearch recognized the strings true, false, on, off, yes, no, 0, 1 as booleans. Elasticsearch 6.0 recognizes only the strings true and false as booleans and will throw an error otherwise. For backwards compatibility purposes, during the 6.x series the previous coercion rules will continue to work on pre-6.0 indices. This means that you do not need ..