不爲也 比不能也

UPDATE: This article refers to our hosted Elasticsearch offering by an older name, Found. Please note that Found is now known as Elastic Cloud.이 게시물은 기존에 Found라는 이름으로 제공된 Elasticsearch 서비스에 관한 것이다. Found은 이제 Elasticsearch Cloud로 알려져 있다.As much as we love Elasticsearch, at Found we've seen customers crash their clusters in numerous ways. Mostly due to simple misunderstandings and usually the fixe..

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에 일치하는 ..

The query phase identifies which documents satisfy the search request, but we still need to retrieve the documents themselves. This is the job of the fetch phase, shown in Figure 15, “분산 검색의 fetch 절”.query 절은 어떤 document가 검색 request를 만족하는지를 확인할 뿐이다. 이제 document 자체를 가져와야 한다. 이것이, Figure 15, “분산 검색의 fetch 절”에서 보이는 fetch 절의 역할이다.Figure 15. 분산 검색의 fetch 절 The distributed phase consists of the follow..

A scroll query is used to retrieve large numbers of documents from Elasticsearch efficiently, without paying the penalty of deep pagination.scroll query는 Elasticsearch에서 매우 많은 수의 document를, deep 페이지 계산의 불이익 없이, 효과적으로 가져오기 위해 함께 사용된다.Scrolling allows us to do an initial search and to keep pulling batches of results from Elasticsearch until there are no more results left. It’s a bit like a cursor ..

Although you can add new types to an index, or add new fields to a type, you can’t add new analyzers or make changes to existing fields. If you were to do so, the data that had already been indexed would be incorrect and your searches would no longer work as expected.index에 새로운 type을 추가하거나 type에 새로운 field를 추가할 있지만, 새로운 analyzer를 추가하거나 기존 field를 변경할 수 없다. 그렇게 하면, 기존의 색인 데이터는 올바르지 않게 되고, 검색은 더 이상 ..

Big, popular forums start out as small forums. One day we will find that one shard in our shared index is doing a lot more work than the other shards, because it holds the documents for a forum that has become very popular. That forum now needs its own index.거대한 인기 있는 포럼은 작은 포럼으로 시작한다. 어느 날, 공유 index의 어떤 shard가 다른 shard보다 훨씬 더 많은 작업을 하고 있는 것을 발견했다. 왜냐하면, 해당 shard가 매우 인기 있는 포럼의 document를 가지고 있기 때..