不爲也 比不能也

Field capabilities request formateditIn the past, fields could be provided either as a parameter, or as part of the request body. Specifying fields in the request body is now deprecated, and instead they should always be supplied through a request parameter. In 7.0.0, the field capabilities API will not accept fieldssupplied in the request body.이전에는, fields 를 매개변수 또는 request body로 제공할 수 있었다. 이제 ..

Concurrency level of analyze requestseditPreviously, analyze requests would run on the same thread pool as indexing requests. The indexthread pool has been deprecated as it is no longer needed since indexing requests are internally converted to bulk requests and run on the bulk thread pool. This leaves analyze requests without a home so we added a small thread pool called the analyze thread pool..

GCS Repository plugineditThe repository settings application_name, connect_timeout and read_timeout have been deprecated and must now be specified in the client settings instead.repository 설정 application_name, connect_timeout, read_timeout은 deprecate되었고, 지금부터는 client 설정에서 지정해야 한다.See Google Cloud Storage Client Settings.Ingest Geoip PlugineditIn earlier versions, database files have been stored ..

Suggest stats metrics deprecatededitThe suggest stats were previously folded into the search on the indices stats API. As such, the suggest metric on the indices stats API has been a synonym for the search metric. In 6.3.0, the suggest metric is deprecated in favor of using search.이전에 suggest stats은 indices stats API의 search에 포함되어 있었다. 따라서, indices stats API의 suggest metric은 search metric의 동의어(s..

A rollover request in Elasticsearch 6.2.0 or later will be aborted if the same alias is found in the matching index templates. This change is to prevent the alias from pointing to multiple indices during rollover. If your index templates already contain the same alias, you should remove it by updating the index templates.Elasticsearch 6.2.0 이후부터, 일치하는 index template에서 동일한 alias가 발견되면, rollover r..

Starting in Elasticsearch 6.2.0, JVM GC logging is enabled out of the box. This lightweight facility gives insight into GC issues. The settings for this are in jvm.options and default to keeping 2 GB worth (rotating every 64 MB) of logs in the default logs directory. If you are upgrading from a previous version of Elasticsearch and preserve your existing jvm.options, you should add the following..

On Linux, previous versions of Elasticsearch defaulted to using /tmp as the temporary directory for the process. However, /tmp is public so we have elected to change the packaging so that we use a private temporary directory. If you are upgrading from a previous version of Elasticsearch and preserve your existing jvm.options, you should add the line -Djava.io.tmpdir=${ES_TMPDIR}. It is safe to d..

All permission bootstrap checkeditElasticsearch installs a security manager during bootstrap to mitigate the scope of exploits in the JDK, in third-party dependencies, and in Elasticsearch itself as well as to sandbox untrusted plugins. A custom security policy can be applied and one permission that can be added to this policy isjava.security.AllPermission. However, this effectively disables the..

Bootstrap checks now apply to link-local addresseseditPreviously when Elasticsearch was bound to localhost, Elasticsearch would bind to any address on the loopback device. This included link-local addresses on the loopback device such as fe80::1%lo0on macOS. Starting in 6.1.2, Elasticsearch will now only bind to loopback addresses on the loopback device. Because of the previous behavior, Elastic..