b83b9d69c9
Currently we suggesting users create a Node (using NodeBuilder in 2.x) to have a client that is capable of keeping up-to-date information. This is generally a bad idea as it means elasticsearch has no control over eg max heap size or gc settings, and is also problematic for users because they must deal with dependency collisions (and in 2.x+ dependencies of elasticsearch itself). A better alternative, and what we should document, is to run a local elasticsearch server using bin/elasticsearch, and then use the transport client to connect to that local node. This local connection is virtually free, and allows the client code to be completely isolated from the elasticsearch process. Plugins are then also easy to deal with: just install them in elasticsearch as usual. Closes #15383 |
||
|---|---|---|
| .. | ||
| admin | ||
| aggregations | ||
| docs | ||
| query-dsl | ||
| aggs.asciidoc | ||
| client.asciidoc | ||
| docs.asciidoc | ||
| index.asciidoc | ||
| indexed-scripts.asciidoc | ||
| percolate.asciidoc | ||
| query-dsl.asciidoc | ||
| search.asciidoc | ||