Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Integrate AEM with Elastic Search 8

Avatar

Level 2

Hi,

 

I'm having trouble in integrating Elastic Search 8 with AEM, specially in dependency and pom management.

My bundle is in Installed state with the following classes not resolved.

 

io.opentelemetry.api.events -- Cannot be resolved
io.opentelemetry.extension.incubator.metrics -- Cannot be resolved
jakarta.json,version=[2.0,3) -- Cannot be resolved
jakarta.json.spi,version=[2.0,3) -- Cannot be resolved
jakarta.json.stream,version=[2.0,3) -- Cannot be resolved

org.apache.http.impl.nio.client -- Cannot be resolved

org.elasticsearch.client -- Cannot be resolved

 

Even though the original ES document just mentions the 2 dependency to be added to pom(Already added)

Link : https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/installation.html#insta...

<project>
  <dependencies>

    <dependency>
      <groupId>co.elastic.clients</groupId>
      <artifactId>elasticsearch-java</artifactId>
      <version>8.10.1</version>
    </dependency>

    <dependency>
      <groupId>com.fasterxml.jackson.core</groupId>
      <artifactId>jackson-databind</artifactId>
      <version>2.12.3</version>
    </dependency>

  </dependencies>
</project>

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi,

 

  1. Check Elasticsearch 8 compatibility with your AEM version.
  2. Examine your bundle's dependencies for conflicts with Elasticsearch.
  3. Use Maven's dependencyManagement to specify dependency versions.
  4. Check for conflicting or duplicate dependencies with mvn dependency:tree.
  5. Consider updating AEM or dependencies to match Elasticsearch 8.
  6. Use a custom classloader to isolate dependencies if needed.

View solution in original post

2 Replies

Avatar

Correct answer by
Employee Advisor

Hi,

 

  1. Check Elasticsearch 8 compatibility with your AEM version.
  2. Examine your bundle's dependencies for conflicts with Elasticsearch.
  3. Use Maven's dependencyManagement to specify dependency versions.
  4. Check for conflicting or duplicate dependencies with mvn dependency:tree.
  5. Consider updating AEM or dependencies to match Elasticsearch 8.
  6. Use a custom classloader to isolate dependencies if needed.

Avatar

Level 2

Upgrading AEM worked for me , thanks for the response.