The official Go client for Elasticsearch.
Starting from version
8.12.0, this library follow the Go language policy. Each major Go release is supported until there are two newer major releases. For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.
Language clients are forward compatible; meaning that clients support communicating with greater or equal minor versions of Elasticsearch. Elasticsearch language clients are only backwards compatible with default distributions and without guarantees made.
When using Go modules, include the version in the import path, and specify either an explicit version or a branch:
require github.com/elastic/go-elasticsearch/v8 v8.0.0 require github.com/elastic/go-elasticsearch/v7 7.17
It's possible to use multiple versions of the client in a single project:
// go.mod github.com/elastic/go-elasticsearch/v7 v7.17.0 github.com/elastic/go-elasticsearch/v8 v8.0.0 // main.go import ( elasticsearch7 "github.com/elastic/go-elasticsearch/v7" elasticsearch8 "github.com/elastic/go-elasticsearch/v8" ) // ... es7, _ := elasticsearch7.NewDefaultClient() es8, _ := elasticsearch8.NewDefaultClient()
main branch of the client is compatible with the current
master branch of Elasticsearch.
Refer to the Installation section of the getting started documentation.
Refer to the Connecting section of the getting started documentation.
- Creating an index
- Indexing documents
- Getting documents
- Searching documents
- Updating documents
- Deleting documents
- Deleting an index
esutil package provides convenience helpers for working with the client. At the moment, it provides the
esutil.JSONReader() and the
_examples folder contains a number of recipes and comprehensive examples to get you started with the client, including configuration and customization of the client, using a custom certificate authority (CA) for security (TLS), mocking the transport for unit tests, embedding the client in a custom type, building queries, performing requests individually and in bulk, and parsing the responses.