不爲也 比不能也

Documents are indexed—stored and made searchable—by using the index API. But first, we need to decide where the document lives. As we just discussed, a document’s _index, _type, and _iduniquely identify the document. We can either provide our own _id value or let the index API generate one for us.document는 index API에 의해 색인된 (저장되고 검색 가능하도록 만들어진)다. 그러나 먼저, document를 어디에 저장할지를 결정해야 한다. 방금 이야기했듯이, d..

How can we be sure, when we index a document, that we are creating an entirely new document and not overwriting an existing one?document를 색인할 때, 기존 document를 덮어쓰는 것이 아니라, 완전히 새로운 것을 생성한다는 것을 어떻게 보장할 수 있을까?Remember that the combination of _index, _type, and _id uniquely identifies a document. So the easiest way to ensure that our document is new is by letting Elasticsearch autogenerate a new uniq..

Elasticsearch is distributed. When documents are created, updated, or deleted, the new version of the document has to be replicated to other nodes in the cluster. Elasticsearch is also asynchronous and concurrent, meaning that these replication requests are sent in parallel, and may arrive at their destination out of sequence. Elasticsearch needs a way of ensuring that an older version of a docu..

In Updating a Whole Document, we said that the way to update a document is to retrieve it, change it, and then reindex the whole document. This is true. However, using the update API, we can make partial updates like incrementing a counter in a single request.Updating a Whole Document에서, document를 업데이트하는 방식은 document를 가져와서 수정하고, 전체 document를 다시 색인 한다고 언급했다. 이것은 사실이다. 그러나 update API를 사용하면, 단일 req..