Release notes, installation instructions, and download archive for the Couchbase Elasticsearch Connector.
Scroll down to the version you want, then click the "Download" link to get the full connector distribution. Refer to Getting Started for detailed installation instructions.
This release adds "uncommitted" support for Collections and Scopes, a new feature planned for Couchbase Server 7.0.
CBES-163: Type definitions now have a
matchOnQualifiedKeyproperty that lets a rule match against the qualified document name, which includes the scope and collection. This enables type definition rules that write to an Elasticsearch index whose name matches the Couchbase collection name.
[couchbase]config section now has optional
collectionproperties that limit the replication to a single scope or to a set of collections.
[couchbase]config section now has optional
metadataCollectionproperty that controls which collection is used to store metadata like replication checkpoints.
CBES-170: If you specify a custom port for a Couchbase host, it can take a long while to connect, and the connector will log lots of warnings about being unable to connect to the KV service.
The workaround is to bootstrap using a KV port (default 11210) instead of a manager port (default 8091), and to explicitly tag the port as belonging to the KV service, like this:
hosts = ['example.com:12345=kv']
The connector now behaves better in environments where DNS entries are highly dynamic. Instead of caching resolved hostnames, it now resolves hostnames prior to every connection attempt.
This release also improves decompression performance, activates Netty native transports, and fixes a bug that prevented the 'couchbase.network' config setting from being honored.
The compatibility matrix is updated to add support for Elasticsearch 7.6 and 7.7. Elasticsearch versions prior to 6.6 are dropped due to end of life, with the exception of 5.6.16.
CBES-155 Couchbase client ignores 'couchbase.network' config setting
This maintenance release addresses an issue with shutdown hooks that could prevent the connector from terminating in some circumstances.
Also fixed in this release, bulk request timeouts longer than 30 seconds are now honored instead of being reduced to 30 seconds.
Metrics from the Couchbase DCP client are now included in the metrics report, along with gauges for CPU load.
Hot on the heels of 4.1, we’re releasing 4.2 with support for connecting directly to an Amazon Elasticsearch Service instance.
There’s a new
[elasticsearch.aws] config section for specifying the AWS region of the service.
Amazon credentials are obtained from the Default Credential Provider Chain.
Also new in 4.2, the
cbes-consul command now takes an optional
--consul-config argument which points to a separate config file where you can specify a Consul ACL token.
On the version compatibility front, we’ve added support for Elasticsearch 7.4 and removed support for Elasticsearch 5.4 (which reached EOL on 2018-11-04).
We are excited to unveil the new Autonomous Operations (AO) mode with major improvements to the availability and manageability of the connector. When the connector is deployed in AO mode, worker processes use your HashiCorp Consul cluster to communicate with each other and automatically distribute the replication workload. You can add or remove worker processes at any time without having to manually stop and reconfigure all of the workers. Any worker that fails a health check is automatically removed, and its workload is redistributed among remaining workers.
cbes-consul command line tool is used to start a worker in AO mode.
It also provides streamlined checkpoint management and the ability to reconfigure or pause/resume all of the workers in an AO group at once.
Also new in this release is support for multi-network configuration.
This feature allows the connector to talk to Couchbase Server nodes that have been configured to advertise alternate network addresses for connecting to the node from outside a container/cloud networking environment.
network property in the
[couchbase] section of the configuration gives you control over network selection (although the default value of
auto is appropriate for most cases).
Finally, the range of supported Elasticsearch versions is extended to include 7.1, 7.2. and 7.3.
This maintenance release fixes a bug that prevented some versions of Couchbase Server from rebalancing when the connector is running.
It also adds compatibility with the official Docker images for Elasticsearch 6.7.x and 7.0.x, and is the first version tested against OpenJDK 8 and OpenJDK 11.
CBES-128 Couchbase Server fails to rebalance if Elasticsearch connector is running
This maintenance release improves the stability of the connector and adds new configuration options.
CBES-117 Connector exits on values that fail to parse
The connector is now a standalone process instead of an Elasticsearch plug-in.
Compatible with Elasticsearch versions 5 and 6.
Support for secure connections to Couchbase and Elasticsearch.
Tools for managing replication checkpoints.
A "rejection log" for documents Elasticsearch permanently refuses to index.
Configurable document structure (omit metadata if you don’t need it).
The connector now listens for document changes using the high performance Couchbase Database Change Protocol (DCP).
|This is a major version upgrade. Because the plug-in and the standalone connector are so different, there is no online upgrade process. See the Migration documentation for details.|
Parent-child relationships are no longer supported, as this feature was removed in ES 6.
Routing documents to specific Elasticsearch shards is not implemented. Please let us know if this feature is still relevant for your deployment.
birch development line has been retired.
cypress line now supports all 5.x versions of Elasticsearch.
RegexParentSelector now reads the parent ID format from the correct config property (
If you previously put the parent ID format in the
documentTypeParentFields property as a workaround, please update your configuration.
The connector can now delete child documents and other documents that have custom routing.
If you’re using
RegexParentSelector then this feature has no additional overhead.
Otherwise, for each document whose routing cannot be derived from the document ID, the connector creates a separate signpost document to record the routing.
Be aware that child documents created by previous versions of the connector are not eligible for deletion, since they don’t have signposts (you’ll see "missing signpost" warnings in the log when the connector tries to delete those documents).
The signposts have a document type of
The mapping for this type must store the contents of the
This is already the case if you’re using the default mapping template included in the plug-in distribution.
With this release, the Couchbase plug-in for Elasticsearch moves to a new versioning and branch management strategy that allows for simultaneous releases across ES versions (see [Version Compatibility]). All the versions are expected to work and are supported. However, versions which have received more testing and are officially supported are:
Don’t be alarmed by the major version bump; upgrading from version 2.x of the plug-in should be seamless, and is recommended for all users. The code has just been relabeled for easier maintenance.
Improves logging for indexing errors.
Uses Dropwizard Metrics to collect and log richer stats.
This release note applies to the 2.2 version of the Elasticsearch Transport Plug-in (February 2017). It adds a number of bug fixes. See Installation and Configuration for versioning and compatibility information.
This release note applies to the 2.1.1 version of the Elasticsearch Transport Plug-in (September 2015). It adds compatibility with newer Elasticsearch versions up to 1.7.x, multiple new features, and quite a few bug fixes, including several that solve issues found in 2.1.0. In particular, this release fixes a long-standing bug with an incorrect concurrent bulk request counter, which could eventually cause the plug-in to stop accepting requests from Couchbase Server altogether.
Some configuration option-names changed.
|Elasticsearch plug-in version||Couchbase versions||Elasticsearch versions|
2.5.x - 4.x
1.3.0 - 1.7.x
This release note is for the Elasticsearch plug-in release 2.0 GA (October 2014). Elasticsearch plug-in version 2.0 is compatible with:
Couchbase Server 3.0
Couchbase Server 2.5.x (backward compatible)
The new feature(s) available in Elasticsearch Plug-in v2.0:
Support more than one document type in Elasticsearch. (MB-12284)
The following are known issues:
att_reasonvalue for non-JSON documents changed from non-JSON mode to invalid_json. If a Couchbase cluster has a lot of deletes, the Elasticsearch log could fill up with a lot of messages. (CBES-31)
This release note is for the Elasticsearch plug-in release 1.3.0 GA (April 2014). This release is compatible only with Elasticsearch 1.0.1.
This release is compatible with Couchbase Server 2.5.x, and it is backward compatible with earlier 2.x releases.
This release note is for the Elasticsearch plug-in release 1.2.0 GA (October 2013). This release adds compatibility with Elasticsearch 0.90.5.
This release is compatible with Couchbase Server 2.2, and it is backward compatible with earlier 2.x releases.
This release note is for the Elasticsearch plug-in release 1.1.0 GA (August 2013). This release adds compatibility with Elasticsearch 0.90.2.
This release note is for the Elasticsearch plug-in release 1.0.0 GA (February 2013). This is the first general availability (GA) release. It contains the following enhancements and bug fixes:
Now compatible with version 0.20.2 of Elasticsearch.
Now supports document expiration using Elasticsearch TTL.
Now supports XDCR conflict resolution to reduce bandwidth usage in some cases.
Fixed Couchbase index template to allow searching on the document metadata.
Fixed data corruption under high load. (CBES-11)
Fixed recognition of non-JSON documents. (CBES-11)
Improved log information when indexing stub documents.