Welcome Guest! Log in
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…


This article describes the principal changes of the Elasticsearch Connector.

The connector download section can be found at this page.

Note:

Stambia DI is a flexible and agile solution. It can be quickly adapted to your needs.

If you have any question, any feature request or any issue, do not hesitate to contact us.

 

addons.elasticsearch_1.1.2

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.

 

addons.elasticsearch_1.1.1

Support document join

This new version supports using the routing value to define joins between documents, as stated in Elasticsearch documentation.

After having reversed a document with a join in your Elasticsearch Metadata, simply add a new value named "routing" at the document's root, and map it in your Mappings.

Refer to this article for further information.

 

addons.elasticsearch_1.1.0

Support of Elasticsearch 7.x

This new version add support for Elasticsearch 7.x server versions.

A new parameter is available in Metadata to select the Elasticsearch server version, which will be used to know which API to use.

Defining this parameter is now mandatory.

Prerequisites:
  • Elasticsearch Templates 2019-06-07 or higher

 

addons.elasticsearch_1.0.6

This version allows to externalize the SSL Security parameters which can be defined on the Elasticsearch Metadata.

For instance, externalizing the following parameters:

externalizeSSLParameters

On previous versions, externalizing those parameters did not work because it was not handled correctly in the Elasticsearch technology and connector.

This has been fixed and the SSL Security parameters can now be correctly externalized.

Note that you'll have to re-generate the Packages of your flows after having installed the new connector version to benefit of the correction.

 

Articles

Suggest a new Article!