mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 07:37:19 -04:00
ac7ce2b899
While we had initially planned to keep rivers around in 2.0 to ease migration, keeping support for rivers is challenging as it conflicts with other important changes that we want to bring to 2.0 like synchronous dynamic mappings updates. Nothing impossible to fix, but it would increase the complexity of how we deal with dynamic mappings updates and manage rivers, while handling dynamic mappings updates correctly is important for resiliency and rivers are on the go. So removing rivers in 2.0 may well be a better trade-off. |
||
|---|---|---|
| .. | ||
| discovery | ||
| gateway | ||
| advanced-scripting.asciidoc | ||
| cluster.asciidoc | ||
| discovery.asciidoc | ||
| gateway.asciidoc | ||
| http.asciidoc | ||
| indices.asciidoc | ||
| memcached.asciidoc | ||
| network.asciidoc | ||
| node.asciidoc | ||
| plugins.asciidoc | ||
| scripting.asciidoc | ||
| snapshots.asciidoc | ||
| threadpool.asciidoc | ||
| thrift.asciidoc | ||
| transport.asciidoc | ||
| tribe.asciidoc | ||