不爲也 比不能也

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

Don’t return large result sets Elasticsearch is designed as a search engine, which makes it very good at getting back the top documents that match a query. However, it is not as good for workloads that fall into the database domain, such as retrieving all documents that match a particular query. If you need to do this, make sure to use the Scroll API.Elasticsearch는 search 엔진으로 설계되어, query에 일치하는 ..

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는 압축된..

How you talk to Elasticsearch depends on whether you are using Java.Elasticsearch와 통신하는 방법은 Java 사용 여부에 달려 있다.Java APIeditIf you are using Java, Elasticsearch comes with two built-in clients that you can use in your code:만약 Java 를 사용한다면, Elasticsearch는, 코드에서 사용할 수 있는, 두 종류의 기본 클라이언트를 제공한다.Node clientThe node client joins a local cluster as a non data node. In other words, it doesn’t hold any dat..