github.com/olivere/elastic/v7
This is a development branch that is actively being worked on. DO NOT USE IN PRODUCTION! If you want to use stable versions of Elastic, please use Go modules for the 7.x release (or later) or a dependency manager like dep for earlier releases.
Elastic is an Elasticsearch client for the Go programming language.
See the wiki for additional information about Elastic.
The release branches (e.g. release-branch.v7)
are actively being worked on and can break at any time.
If you want to use stable versions of Elastic, please use Go modules.
Here's the version matrix:
| Elasticsearch version | Elastic version | Package URL | Remarks |
|---|---|---|---|
| 7.x | 7.0 | github.com/olivere/elastic/v7 (source doc) | Use Go modules. |
| 6.x | 6.0 | github.com/olivere/elastic (source doc) | Use a dependency manager (see below). |
| 5.x | 5.0 | gopkg.in/olivere/elastic.v5 (source doc) | Actively maintained. |
| 2.x | 3.0 | gopkg.in/olivere/elastic.v3 (source doc) | Deprecated. Please update. |
| 1.x | 2.0 | gopkg.in/olivere/elastic.v2 (source doc) | Deprecated. Please update. |
| 0.9-1.3 | 1.0 | gopkg.in/olivere/elastic.v1 (source doc) | Deprecated. Please update. |
Example:
You have installed Elasticsearch 7.0.0 and want to use Elastic.
As listed above, you should use Elastic 7.0 (code is in release-branch.v7).
To use the required version of Elastic in your application, you
should use Go modules
to manage dependencies. Make sure to use a version such as 7.0.0 or later.
To use Elastic, import:
import "github.com/olivere/elastic/v7"
Elastic 7.0 targets Elasticsearch 7.x which was released on April 10th 2019.
As always with major version, there are a lot of breaking changes. We will use this as an opportunity to clean up and refactor Elastic, as we already did in earlier (major) releases.
Elastic 6.0 targets Elasticsearch 6.x which was released on 14th November 2017.
Notice that there are a lot of breaking changes in Elasticsearch 6.0 and we used this as an opportunity to clean up and refactor Elastic as we did in the transition from earlier versions of Elastic.
Elastic 5.0 targets Elasticsearch 5.0.0 and later. Elasticsearch 5.0.0 was released on 26th October 2016.
Notice that there are will be a lot of breaking changes in Elasticsearch 5.0 and we used this as an opportunity to clean up and refactor Elastic as we did in the transition from Elastic 2.0 (for Elasticsearch 1.x) to Elastic 3.0 (for Elasticsearch 2.x).
Furthermore, the jump in version numbers will give us a chance to be in sync with the Elastic Stack.
Elastic 3.0 targets Elasticsearch 2.x and is published via gopkg.in/olivere/elastic.v3.
Elastic 3.0 will only get critical bug fixes. You should update to a recent version.
Elastic 2.0 targets Elasticsearch 1.x and is published via gopkg.in/olivere/elastic.v2.
Elastic 2.0 will only get critical bug fixes. You should update to a recent version.
Elastic 1.0 is deprecated. You should really update Elasticsearch and Elastic to a recent version.
However, if you cannot update for some reason, don't worry. Version 1.0 is still available. All you need to do is go-get it and change your import path as described above.
We use Elastic in production since 2012. Elastic is stable but the API changes now and then. We strive for API compatibility. However, Elasticsearch sometimes introduces breaking changes and we sometimes have to adapt.
Having said that, there have been no big API changes that required you to rewrite your application big time. More often than not it's renaming APIs and adding/removing features so that Elastic is in sync with Elasticsearch.
Elastic has been used in production starting with Elasticsearch 0.90 up to recent 7.x versions. We recently switched to GitHub Actions for testing. Before that, we used Travis CI successfully for years).
Elasticsearch has quite a few features. Most of them are implemented by Elastic. I add features and APIs as required. It's straightforward to implement missing pieces. I'm accepting pull requests :-)
Having said that, I hope you find the project useful.
The first thing you do is to create a Client.
The client connects to Elasticsearch on http://127.0.0.1:9200 by default.
You typically create one client for your app. Here's a complete example of creating a client, creating an index, adding a document, executing a search etc.
An example is available here.
Here's a link to a complete working example for v6.
Here are a few tips on how to get used to Elastic:
_test.go files).
They not only serve as a guard against changes, but also as a reference.Scrolling is supported via a ScrollService. It supports an iterator-like interface.
The ClearScroll API is implemented as well.
A pattern for efficiently scrolling in parallel is described in the Wiki.
Read the contribution guidelines.
Thanks a lot for the great folks working hard on Elasticsearch and Go.
Elastic uses portions of the uritemplates library by Joshua Tacoma, backoff by Cenk Altı and leaktest by Ian Chiles.
MIT-LICENSE. See LICENSE or the LICENSE file provided in the repository for details.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.