不爲也 比不能也

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

This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 2.2.여기에서는 application을 Elasticsearch 2.2 로 migration할 경우 알아야 할 변경 사항에 대해 이야기한다.Geo Point TypeeditThe geo_point format has been changed to reduce index size and the time required to both index and query geo point data. To make these performance improvements possible both doc_values and..

Cluster-health is at one end of the spectrum—a very high-level overview of everything in your cluster. The node-stats API is at the other end. It provides a bewildering array of statistics about each node in your cluster.cluster-health 는 cluster의 모든 것에 대한 매우 높은 수준의 개요 부분이다. node-stats API는 또 다른 부분이다. 이것은 cluster의 각 node에 대한 복잡한 통계의 배열을 제공한다.Node-stats provides so many stats that, until you are a..

The cluster-stats API provides similar output to the node-stats. There is one crucial difference: Node Stats shows you statistics per node, while cluster-stats shows you the sum total of all nodes in a single metric.cluster-stats API는 node-stats 와 유사한 출력을 제공한다. 결정적인 차이점이 하나 있는데, node-stats 는 node 별 통계를 보여주는 반면에, cluster-stats 는 모든 node의 총 합을 하나의 통계로 보여준다.This provides some useful stats to glance..

So far, we have been looking at node-centric statistics: How much memory does this node have? How much CPU is being used? How many searches is this node servicing?지금까지, node 중심 의 통계를 살펴봤다. 이 node가 가지고 있는 메모리가 얼마인지? CPU가 얼마나 사용되고 있는지? 이 node가 서비스하고 있는 검색은 얼마나 많은지?Sometimes it is useful to look at statistics from an index-centric perspective: How many search requests is this index receiving? How m..