Steps for using SQL implementation (with PostgreSQL)

[stratosEft]

Hi everyone,

I am using the MVD and want to add the SQL module, but so far my configuration doesn't work. Probably a valid configuration will also help others that may face the same problem, so I would like some help on doing so.

I work on a snapshot of the connector (0.3.1) since it is compatible with the MVD_UI and didn't update since it seems a very stable version.

On the connector side:

• I have added the sql module implementation(project(":extensions:control-plane:store:sql:control-plane-sql")) to the data-plane-server launcher ./launchers/data-plane-server/build.gradle.kts in order to be initialised.

• The config.properties file within the same folder of the launcher (should this config be added here or on the MVD side?) has the following properties: (*values are removed just for the discussion)

edc.datasource.default.url=
edc.datasource.default.user=
edc.datasource.default.password=

Also tried to add properties for all sources:

edc.datasource.default.user=
edc.datasource.default.password=
edc.datasource.default.url=

edc.datasource.asset.name=
edc.datasource.asset.url=
edc.datasource.asset.user=
edc.datasource.asset.password=

edc.datasource.contractdefinition.name=
edc.datasource.contractdefinition.url=
edc.datasource.contractdefinition.user=
edc.datasource.contractdefinition.password=

edc.datasource.transferprocess.name=
edc.datasource.transferprocess.url=
edc.datasource.transferprocess.user=
edc.datasource.transferprocess.password=

edc.datasource.policy.name=
edc.datasource.policy.user=
edc.datasource.policy.password=
edc.datasource.policy.url=

On the MVD side:

• Used the default setup ( 1 provider, 2 consumers) and initialised 3 different PostgreSQL instances using the provided SQL schema for each connector

-> what is working as expected with this configuration

• Create assets
• Create contract definitions
• Negotiate an asset
• See the contract

-> what is not working as expected with this configuration

• Save a Policy
• transfer Asset

*All DB Tables are created, but the tables for policy-definition-store-sql edc_policydefinitions and transfer-process-store-sql edc_transfer_process are always empty...

The InMemory stores work as expected and everything is completed without issues.

Any thoughts on what is missing here? Thank you in advance.

@ndr-brt @juliapampus Thank you for your help so far!

[ndr-brt]

hey, could you please provide some stack traces and details about the error you are seeing?

[a-tsal]

Hello the thrown error is:

org.eclipse.edc.spi.persistence.EdcPersistenceException: org.eclipse.edc.spi.persistence.EdcPersistenceException: com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot construct instance of org.eclipse.edc.connector.transfer.spi.types.ResourceDefinition$Builder(no Creators, like default constructor, exist): cannot deserialize from Object value (no delegate- or property-based Creator) company2 | at [Source: (String)"{"definitions":[{"edctype":"ObjectStorageResourceDefinition","id":"97fcfa0b-fe02-4e1f-873d-15e0c2e41950","transferProcessId":"6a9db54b-eb3e-4b92-a10d-33aa8b8c93d2","containerName":"7a9c53c7-d54f-4644-bbf5-204f46250824","accountName":"company2assets"}]}"; line: 1, column: 62] (through reference chain: org.eclipse.edc.connector.transfer.spi.types.ResourceManifest$Builder["definitions"]->java.util.ArrayList[0])

and it obviously has something to do with the deserialization process

[veirigoyen]

Hello everyone,

I’m facing the same issue. Has anyone found a solution or any updates on this?
I’d really appreciate any insights.

Thanks in advance!

[wolf4ood]

Hi @veirigoyen

the MVD kubernetes deployment already supports persistence checks here

https://github.com/eclipse-edc/MinimumViableDataspace?tab=readme-ov-file#5-running-the-demo-kubernetes

[paullatzelsperger]

please note that version 0.3.1 is very outdated. we can't help you until you upgrade to the current version.

[paullatzelsperger]

I'll close this discussion, because a) you are using an outdated/unsupported version of EDC, and b) the MVD already supports persistence as outlined by @wolf4ood