Elasticsearch Component Release Notes

This page lists the main features added to the Elasticsearch Component.

Feature Highlights

Version 2.2.0

Bug fixes

This version fixes a list of issues which can be found on the full changelog.

Version 2.1.0

Support of EMF Compare

Several improvements have been made to support EMF Compare.

Version 2.0.5

Bug fixes

This version fixes a list of issues which can be found on the full changelog.

Version 2.0.4

Ability to choose communication protocol

Elasticsearch Component was using Elasticsearch’s Transport protocol to communicate with and perform operations on Elasticsearch.

This protocol has been deprecated by Elasticsearch, which currently recommends using the HTTP/REST protocol.

This new Elasticsearch Component version supports using the HTTP/REST protocol for communicating with Elasticsearch.

A new attribute has been added to allow choosing which protocol to use.

Default selected protocol is "Transport" for backward compatibility.

Below, some information about the two protocols.

Transport protocol

Transport protocol is the legacy Elasticsearch protocol which was the default protocol used by Elasticsearch Component.

It is supported by Elasticsearch until Elasticsearch version 7.

It is currently deprecated by Elasticsearch, and later versions will not support it.

HTTP/REST protocol

HTTP/REST Elasticsearch protocol.

It is the currently recommended protocol client by Elasticsearch.

It is supported from Elasticsearch 5.6 and higher versions.

Choose the protocol in the Metadata

In Elasticsearch Metadata, you can select the new protocol on the main server node.

Default value is Transport for backward compatibility.

elasticsearch release notes protocol list

The HTTP Protocol cannot be used with Elasticsearch Version 2.

Elasticsearch 2.x legacy support

Elasticsearch 2.x support is now kept as legacy and compatibility purposes, as this version is not supported anymore by Elasticsearch.

Only maintenance and critical fixes will be performed on Elasticsearch 2.x.

Change Data Capture (CDC)

Multiple improvements have been performed to homogenize the usage of Change Data Capture (CDC) in the various Components.

Parameters have been homogenized, so that all Templates should now have the same CDC Parameters, with the same support of features.

Multiple fixes have also been performed to correct CDC issues. Refer to the changelog for the exact list of changes.

Version 2.0.3

Support Xpack Security

Xpack security is now supported by the Component.

You can define a new Xpack security node under your Elasticsearch Metadata.

Define the required properties on it, which may differ depending on your Xpack configuration.

elasticsearch release notes xpack security

And then use this Xpack node as security by selecting it on the security attribute which is on the server node.

Ability to limit the number of hits returned when performing searches

A new parameter is available on Search Template to limit the number of hits to return.

It is named "ESearch Hit Limit" and defaults to "-1" to retrieve all hits.

Bug fixes

This version fixes a list of issues which can be found on the full changelog.

Most notably, it fixes issues with cluster name and Search Guard properties which were ignored.

Do not hesitate to take a look at it to have an idea of what have changed.

Version 2.0.2

Sample project

The component example project can now be imported directly in the "New" menu of the Project Explorer.

Version 2.0.1

XPath Functions

Addition of new XPath functions to access the various SSL and HTTP attributes values.

It can be used when needing to retrieve those information in various places, and will be used when necessary in Templates.

Change Log

Version 2023.1.0

Bug Fixes

  • DI-6147: Remove unsupported ELasticsearch versions (2.x, 5.4, 6.x).

  • DI-6149: Multiple third-party libraries upgrade.

  • DI-6315: SnakeYAML - Third-party library upgrade.

Version 2.0.3 (Elasticsearch Component)

New Features

  • DI-2806: Support Xpack Security

  • DI-2826: When performing a search operation, it is now possible to limit the number of hits returned through a new parameter available on the corresponding template

Bug Fixes

  • DI-2689: Search Guard properties were ignored, avoiding connecting to Search Guard secured Elasticsearch servers

  • DI-2805: The cluster-name specified in Metadata is ignored, which leads to connection errors when working with an elasticsearch server having a custom cluster-name

  • DI-2824: Search operation is throwing an error if returned data contains special characters

  • DI-2825: Search operation was not handling properly some of the query parameters, such as includes, excludes, …​ which were ignored

  • DI-2839: Elasticsearch default encoding used when performing operations should be UTF-8

Version 2.0.4 (Elasticsearch Component)

New Features

  • DI-1718: Support communicating with Elasticsearch through HTTP/REST protocol

  • DI-2209: Elasticsearch 2 support is now kept as legacy and compatibility purposes, as this version is not supported anymore by Elasticsearch. Only maintenance and critical fixes will be performed on Elasticsearch 2.x.

  • DI-1910: Templates updated - New parameter 'Cdc Subscriber' on Templates on which it was not handled yet

  • DI-1909: Templates updated - New Parameters 'Unlock Cdc Table' and 'Lock Cdc Table' to configure the behaviour of CDC tables locking

Version 2.0.5 (Elasticsearch Component)

Bug Fixes

  • DI-3130: Elasticsearch - Defined HTTP password was not taken into account when performing an Elasticsearch Query operation on a secured Elasticsearch server

Version 2.1.0 (Elasticsearch Component)

New Features

  • DI-3510: EMF compare utility - Component has been updated to support EMF Compare comparison utility

Version 2.2.0 (Elasticsearch Component)

Bug Fixes

  • DI-2892: Elasticsearch Metadata - "HTTP/REST" protocol should not be proposed in Metadata when Elasticsearch 2 version is selected as it is not supported with this Elasticsearch version

Version 3.0.0 (Component Pack)

New Features

  • DI-3701: Allow Components to contribute to Designer monitored statistics

  • DI-4508: Update Components and Designer to take into account dedicated license permissions

  • DI-4962: Improved component dependencies and requirements management

Bug Fixes

  • DI-5087: Update Log4 third-party library (CVE-2021-44228)

Version 3.0.2 (Component Pack)

Bug Fixes

  • DI-5189 : Update Log4 third-party library (CVE-2021-44228).