search

VirtualFlyBrain / neo4j2owl

Semantics preserving mapping of OWL 2 EL and Neo4J. Under development, do not use.
Apache License 2.0
6 stars 3 forks source link

Update neo4j to 3.x or 4.x #61

Open matentzn opened 3 years ago

matentzn commented 3 years ago

To move the neo4j2owl plugin to be compatible with anything after 3.4.X

you need to update the pom.xml in neo4j2owl, something like: https://github.com/VirtualFlyBrain/neo4j2owl/pull/57/files

However, just try to get straight to neo 4 (latest version).

The problem is that some of the Neo4j Database API use has been deprecated; changed..

Some of the necessary changes were not clear to me.

The problem with the integration is that the integration itself will not work with the new version. after you adopt to new version, it passing will give you 97.6 % certainty that it works.

matentzn commented 3 years ago

API calls detailed here may have changed: https://github.com/VirtualFlyBrain/neo4j2owl#implementation

Other potential points of failure:

1) python API (changes to bolt API) 2) changes to REST API 3) changes CYPHER (scary!)

dosumis commented 3 years ago

@hkir-dev to look into migration of code @Robbie1977 to try simple approach of making DB dump and loading into new version DB with standard migration code from neo4j.

hkir-dev commented 3 years ago

new branch (migrate_neo4j_hk) created. Neo4j updated to 4.2.3 and jdk updated to 11. Local unit tests are successful. Integration tests will take place after the release of new image.