Liferay DXP Elasticsearch Connectors: Technical Data Sheet

Introduction

This article extends the Search Engine Compatibility Matrix to provide technical information about Liferay's Elasticsearch* connectors.

Notes on Liferay Enterprise Search (LES)
The LES connectors are omitted from this article as they are not server connectors: they do not instantiate clients to communicate with Elasticsearch nodes, but rather extend the capabilities of our Elasticsearch connectors.

DXP Patch Levels & Marketplace Versions
The information in this article applies to the versions listed below available DXP versions (Fix Pack level or Marketplace version) unless indicated otherwise. This article will be updated as changes are required.

  • DXP 7.4 Update 110, 2023.Q4
  • DXP 7.3 Update 35
  • DXP 7.2 FP20
  • DXP 7.1 FP27
  • DXP 7.0 FP102
  • Liferay Connector to Elasticsearch 7 v3.5.0 (for DXP 7.2)
  • Liferay Connector to Elasticsearch 7 v2.2.0 (for DXP 7.1)
  • Liferay Connector to Elasticsearch 6 v1.3.1 (for DXP 7.0)
    Latest Update: January 30, 2024

Table of Contents

DXP 7.4

Applies to the DXP Quarterly Releases as well.

Name Availability Fix/Support Fix Delivery Method Elasticsearch Client Type1
Elasticsearch Client Lib Version2  Communication Protocol Supports Secure Connection (TLS/SSL, user authentication) Compatible Elasticsearch Version3  JVM Requirement4 
Liferay Connector to Elasticsearch 7
Bundled (default) Update/Hotfix REST Client (Java) 7.17.14 HTTP Yes, out-of-the-box (HTTPS)

8.8.x - 8.12.x

7.17.x

No

The connector configuration’s Operation Mode (operationMode) setting is deprecated and replaced with Production Mode Enabled (productionModeEnabled). The Embedded operation mode has been replaced with a Sidecar Elasticsearch server as of DXP 7.3.

1 We mostly use the High Level REST Client, however, there are some currently unimplemented features that DXP needs so we obtain the Low Level REST Client from the High-Level client to build the necessary JSON for the requests.

2 Refers to the client library version the connector uses. The version of the Sidecar Elasticsearch server started when the portal first starts and the connector is not yet configured for Production mode may be using a newer minor version, but its version is never lower than the client version.

3 Liferay conducts ad-hoc testing of the Elasticsearch connectors with minor releases of Elasticsearch to ensure that Liferay DXP features are also compatible with newer minor versions. As these minor releases sometimes introduce breaking changes, the Search Engine Compatibility Matrix is updated only after successful iterations. The Elasticsearch 8.x compatibility is provided through the REST API Compatibility.

4 The Java REST Client communicates with Elasticsearch over HTTP. This communication protocol does not require Java serialization between DXP and Elasticsearch as opposed to the previous Transport Client-based connectors. Your Elasticsearch nodes can run on different JVM than what your DXP deployment is using.

 

DXP 7.3

Name Availability Fix/Support Fix Delivery Method Elasticsearch Client Type1 Elasticsearch Client Lib Version2 Communication Protocol Supports Secure Connection (TLS/SSL, user authentication) Compatible Elasticsearch Version3 JVM Requirement4
Liferay Connector to Elasticsearch 7
Bundled (default) Update/Hotfix REST Client (Java) 7.16.3 HTTP Yes, out-of-the-box (HTTPS)

8.8.x- 8.12.x,

7.16.x - 7.17.x

No

The connector configuration’s Operation Mode (operationMode) setting is deprecated and replaced with Production Mode Enabled (productionModeEnabled). The Embedded operation mode has been replaced with a Sidecar Elasticsearch server as of DXP 7.3.

1 We mostly use the High Level REST Client, however, there are some currently unimplemented features that DXP needs so we obtain the Low Level REST Client from the High-Level client to build the necessary JSON for the requests.

2 Refers to the client library version the connector uses. The version of the Sidecar Elasticsearch server started when the portal first starts and the connector is not yet configured for Production mode may be using a newer minor version, but its version is never lower than the client version.

3 Liferay conducts ad-hoc testing of the Elasticsearch connectors with minor releases of Elasticsearch to ensure that Liferay DXP features are also compatible with newer minor versions. As these minor releases sometimes introduce breaking changes, the Search Engine Compatibility Matrix is updated only after successful iterations. The Elasticsearch 8.x compatibility is provided through the REST API Compatibility.

4 The Java REST Client communicates with Elasticsearch over HTTP. This communication protocol does not require Java serialization between DXP and Elasticsearch as opposed to the previous Transport Client-based connectors. Your Elasticsearch nodes can run on different JVM than what your DXP deployment is using.

DXP 7.2

Name Availability Fix/Support Fix Delivery Method Elasticsearch Client Type Elasticsearch Client Lib Version1 Communication Protocol Supports Secure Connection (TLS/SSL, user authentication) Compatible Elasticsearch Version2 Operation Modes JVM Requirement3
Liferay Connector to Elasticsearch 6 Bundled (default) Fix Pack/Hotfix Transport Client (Java) 6.8.15 Transport level Yes, through the Liferay Enterprise Search Security (v3.x)4 6.8.x EMBEDDED, REMOTE Yes
Liferay Connector to Elasticsearch 7 Marketplace (v3.x) Marketplace release/Hotfix LPKG Transport Client (Java) 7.17.13 Transport level Yes, out-of-the-box (doc) 7.17.x EMBEDDED, REMOTE Yes

 

1 Refers to the client library versions the connector uses as dependencies at compile time. This also defines the version of the Elasticsearch server started in EMBEDDED mode when the portal first starts and the connector is not yet configured for REMOTE mode.

2 Liferay conducts ad-hoc testing of the Elasticsearch connectors with minor releases of Elasticsearch. These minor releases sometimes introduce breaking changes at the low-level Java API. Therefore, both Liferay and Elastic recommend that the version of the server and the clients match. Elastic says:

"The client must have the same major version (e.g. 2.x, or 5.x) as the nodes in the cluster. Clients may connect to clusters which have a different minor version (e.g. 2.3.x) but it is possible that new functionality may not be supported. Ideally, the client should have the same version as the cluster."

3 The Transport Client relies on Java serialization. Because of this, the Major version and the Vendor of the JVM used by DXP and Elasticsearch must be the same. If Subscription Services' investigation determines that the root cause of the issue is related to a JDK mismatch, then Subscription Services will be limited in resolving the issue.

4 Requires Liferay Enterprise Search (LES) subscription. Liferay Connector to X-Pack Security [Elastic Stack 6.x] has been renamed to Liferay Enterprise Search Security in September, 2020.

 

DXP 7.1

Name Availability Fix/Support Fix Delivery Method Elasticsearch Client Type Elasticsearch Client Lib Version1 Communication Protocol Supports Secure Connection (TLS/SSL, user authentication) Compatible Elasticsearch Version2 Operation Modes JVM Requirement3
Liferay Connector to Elasticsearch 6 Bundled (default) Fix Pack/Hotfix Transport Client (Java) 6.8.6 Transport level Yes, through the Liferay Enterprise Search Security (v2.x)4 6.8.x EMBEDDED, REMOTE Yes
Liferay Connector to Elasticsearch 7 Marketplace (v2.x) Marketplace release/Hotfix LPKG Transport Client (Java) 7.17.13 Transport level Yes, out-of-the-box (doc) 7.17.x EMBEDDED, REMOTE Yes

 

1 Refers to the client library versions the connector uses as dependencies at compile time. This also defines the version of the Elasticsearch server started in EMBEDDED mode when the portal first starts and the connector is not yet configured for REMOTE mode.

2 Liferay conducts ad-hoc testing of the Elasticsearch connectors with minor releases of Elasticsearch. These minor releases sometimes introduce breaking changes at the low-level Java API. Therefore, both Liferay and Elastic recommend that the version of the server and the clients match. Elastic says:

"The client must have the same major version (e.g. 2.x, or 5.x) as the nodes in the cluster. Clients may connect to clusters which have a different minor version (e.g. 2.3.x) but it is possible that new functionality may not be supported. Ideally, the client should have the same version as the cluster."

3 The Transport Client relies on Java serialization. Because of this, the Major version and the Vendor of the JVM used by DXP and Elasticsearch must be the same. If Subscription Services' investigation determines that the root cause of the issue is related to a JVM mismatch, then Subscription Services will be limited in resolving the issue.

4 Requires Liferay Enterprise Search (LES) subscription. Liferay Connector to X-Pack Security [Elastic Stack 6.x] has been renamed to Liferay Enterprise Search Security in September, 2020.

 

DXP 7.0

Name Availability Fix/Support Fix Delivery Method Elasticsearch Client Type Elasticsearch Client Lib Version1 Communication Protocol Supports Secure Connection (TLS/SSL, user authentication) Compatible Elasticsearch Version2 Operation Modes JVM Requirement3
Liferay Portal Search Elasticsearch Bundled (default) Fix Pack/Hotfix Transport Client (Java) 2.4.0 Transport level Yes, through the Shield plugin4 2.4.x EMBEDDED, REMOTE Yes
Liferay Connector to Elasticsearch 6 Marketplace (v1.x) Marketplace release/Hotfix LPKG Transport Client (Java) 6.8.15 Transport level Yes, through the Liferay Enterprise Search Security (v1.x)4 6.8.x EMBEDDED, REMOTE Yes

 

1 Refers to the client library versions the connector uses as dependencies at compile time. This also defines the version of the Elasticsearch server started in EMBEDDED mode when the portal first starts and the connector is not yet configured for REMOTE mode.

2 Liferay conducts ad-hoc testing of the Elasticsearch connectors with minor releases of Elasticsearch. These minor releases sometimes introduce breaking changes at the low-level Java API. Therefore, both Liferay and Elastic recommend that the version of the server and the clients match. Elastic says:

"The client must have the same major version (e.g. 2.x, or 5.x) as the nodes in the cluster. Clients may connect to clusters which have a different minor version (e.g. 2.3.x) but it is possible that new functionality may not be supported. Ideally, the client should have the same version as the cluster."

3 The Transport Client relies on Java serialization. Because of this, the Major version and the Vendor of the JVM used by DXP and Elasticsearch must be the same. If Subscription Services' investigation determines that the root cause of the issue is related to a JDK mismatch, then Subscription Services will be limited in resolving the issue.

4 Requires Liferay Enterprise Search (LES) subscription. Liferay Connector to X-Pack Security [Elastic Stack 6.x] has been renamed to Liferay Enterprise Search Security in September, 2020.

 


* Elastic, Elasticsearch, and X-Pack are trademarks of Elasticsearch BV, registered in the U.S. and in other countries.

¿Fue útil este artículo?
Usuarios a los que les pareció útil: 0 de 1