不爲也 比不能也

Java programmers have two choices when communicating with Elasticsearch: they can use either the REST API over HTTP, or the internal Java API used by Elasticsearch itself for node-to-node communication.Java programmer는 Elasticsearch와 통신 할 경우, 두 가지 중 하나를 선택을 할 수 있다. HTTP를 통한 REST API 또는 Elasticsearch 자체에서 node 간 통신을 위해 사용하는 내부 Java API를 사용할 수 있다.So, what's the difference between these two APIs? W..

Java High Level REST ClienteditStarting from version 5.6.0 a new Java client has been released: the Java High Level REST Client. This official high-level client (named like this to differentiate it from the existing low-level client) for Elasticsearch can be used to execute search, index, delete, update and bulk operations using the same Core Java classes as the TransportClient uses.5.6.0 부터는 새로..

Packaging changeseditLogging configurationeditPreviously Elasticsearch exposed a single system property (es.logs) that included the absolute path to the configured logs directory, and the prefix of the filenames used for the various logging files (the main log file, the deprecation log, and the slow logs). This property has been replaced in favor of three properties:이전 Elasticsearch에서는 설정된 logs ..

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