不爲也 比不能也

Anybody who uses Elasticsearch for indexing time-based data such as log events is accustomed to the index-per-day pattern: use an index name derived from the timestamp of the logging event rounded to the nearest day, and new indices pop into existence as soon as they are required. The definition of the new index can be controlled ahead of time using index templates.log event처럼 시간 기반의 data를 index..

A rollover request in Elasticsearch 6.2.0 or later will be aborted if the same alias is found in the matching index templates. This change is to prevent the alias from pointing to multiple indices during rollover. If your index templates already contain the same alias, you should remove it by updating the index templates.Elasticsearch 6.2.0 이후부터, 일치하는 index template에서 동일한 alias가 발견되면, rollover r..

Indices API changeseditAlias names are validated against (most of) the rules for index nameseditAlias names are now validated against almost the same set of rules that validate index names. The only difference is that aliases are allowed to have uppercase characters. That means that aliases may not:이제 alias 이름은 index 이름에 대한 유효성 검사와 거의 동일한 규칙 집합으로, 유효성 검사가 수행됩니다. 유일한 차이점은 alias에서는 대문자가 허용된다는 것이다...

Closing / deleting indices while running snapshoteditIn previous versions of Elasticsearch, closing or deleting an index during a full snapshot would make the snapshot fail. In 5.0, the close/delete index request will fail instead. The behavior for partial snapshots remains unchanged: Closing or deleting an index during a partial snapshot is still possible. The snapshot result is then marked as ..

Index aliaseseditFields used in alias filters no longer have to exist in the mapping at alias creation time. Previously, alias filters were parsed at alias creation time and the parsed form was cached in memory. Now, alias filters are parsed at request time and the fields in filters are resolved from the current mapping.alias filter에 사용되는 field는 더 이상 alias 생성 시에 mapping에 존재할 필요가 없다. 이전 버전에서, ali..

The problem with the reindexing process described previously is that you need to update your application to use the new index name. Index aliases to the rescue!위에서 언급한 reindex 프로세스의 문제점은, 새로운 index 이름을 사용하기 위해, 응용프로그램을 업데이트해야 한다는 점이다. index alias가 해결책이다.An index alias is like a shortcut or symbolic link, which can point to one or more indices, and can be used in any API that expects an index nam..

Finally, remember that there is no rule that limits your application to using only a single index. When we issue a search request, it is forwarded to a copy (a primary or a replica) of all the shards in an index. If we issue the same search request on multiple indices, the exact same thing happens—there are just more shards involved.마지막으로, 응용프로그램이 단일 index만을 사용하도록 제한하는 규칙은 없다는 점을 기억하자. 어떤 검색 req..

To keep our design simple and clean, we would like our application to believe that we have a dedicated index per user—or per forum in our example—even if the reality is that we are using one big shared index. To do that, we need some way to hide the routing value and the filter onforum_id.간단하게 말하면, 실제로는 하나의 큰 shared index를 사용하고 있지만, 응용프로그램이 사용자 별로(예제에서는 포럼 별로) 전용 index가 있다고 믿게 하고 싶다. 이를 위해, rout..

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를 가지고 있기 때..