Using federatedcatalog-feature-sql-bom may result in java.lang.IncompatibleClassChangeError

[thomasrutger]

Bug Report

Describe the Bug

Using the federatedcatalog-feature-sql-bom may result in a java.lang.IncompatibleClassChangeError,.

Expected Behavior

No exception.

Observed Behavior

A java.lang.IncompatibleClassChangeError is thrown.

│ SEVERE 2025-01-25T21:18:33.67145486 Unexpected error during plan execution                                                                                                                                                                 │
│ java.lang.IncompatibleClassChangeError: Class org.eclipse.edc.catalog.store.sql.schema.postgres.PostgresDialectStatements does not implement the requested interface org.eclipse.edc.catalog.store.sql.TargetNodeStatements                │
│     at org.eclipse.edc.catalog.store.sql.SqlTargetNodeDirectory.lambda$getAll$0(SqlTargetNodeDirectory.java:47)                                                                                                                            │
│     at org.eclipse.edc.transaction.local.LocalTransactionContext.execute(LocalTransactionContext.java:74)                                                                                                                                  │
│     at org.eclipse.edc.catalog.store.sql.SqlTargetNodeDirectory.getAll(SqlTargetNodeDirectory.java:45)                                                                                                                                     │
│     at org.eclipse.edc.catalog.cache.ExecutionManager.fetchWorkItems(ExecutionManager.java:171)                                                                                                                                            │
│     at org.eclipse.edc.catalog.cache.ExecutionManager.doWork(ExecutionManager.java:81)                                                                                                                                                     │
│     at org.eclipse.edc.catalog.cache.ExecutionManager.lambda$executePlan$1(ExecutionManager.java:73)                                                                                                                                       │
│     at org.eclipse.edc.crawler.spi.model.RecurringExecutionPlan.lambda$catchExceptions$0(RecurringExecutionPlan.java:52)                                                                                                                   │
│     at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)                                                                                                                                                   │
│     at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)                                                                                                                                                          │
│     at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)                                                                                                            │
│     at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)                                                                                                                                           │
│     at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)                                                                                                                                           │
│     at java.base/java.lang.Thread.run(Thread.java:833)             

Steps to Reproduce

Create a runtime with the federatedcatalog-feature-sql-bom and run it.

Context Information

Add any other context about the problem here.

EDC v0.11.0

Detailed Description

If applicable, add screenshots and logs to help explain your problem.

Possible Implementation

The modules federated-catalog-cache-sql and target-node-directory-sql both contain classes with the exact same fully qualified class name, causing problems when resolving the class (in particular PostgresDialectStatements). Renaming package/class names in one of these modules should fix this.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[ndr-brt]

@thomasrutger would you like to come up with a PR for this?

[thomasrutger]

@thomasrutger would you like to come up with a PR for this?

Sure, no problem!

[github-actions]

This issue is stale because it has been open for 28 days with no activity.