Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using Neo4j for the storage #282

Closed
dcoraboeuf opened this issue Jun 26, 2015 · 0 comments
Closed

Consider using Neo4j for the storage #282

dcoraboeuf opened this issue Jun 26, 2015 · 0 comments

Comments

@dcoraboeuf
Copy link
Contributor

dcoraboeuf commented Jun 26, 2015

Using Neo4J instead of H2 could help in 1) reducing the footprint of the database storage 2) simplifying the maintenance of the schema. Ontrack structure is actually a graph of relation ships between different entities.

This would need to be done for a version 4 of Ontrack, with a necessary migration step from the H2 database to the Neo4j graph database. This could be done by a tool and not necessarily from within the Ontrack application.

In a first phase, only add a module, in versions 2 & 3, to export Ontrack data as a set of CSV files, suitable to be imported in a Neo4j database.

When the export is mature and well tested, start creating a version 4 to use Neo4J as backend.

@dcoraboeuf dcoraboeuf added type: feature v3 Planned for version 3 labels Jun 26, 2015
@dcoraboeuf dcoraboeuf added v4 Planned for version 4 and removed v3 Planned for version 3 labels May 4, 2016
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 4, 2017
dcoraboeuf added a commit that referenced this issue Feb 5, 2017
dcoraboeuf added a commit that referenced this issue Feb 5, 2017
dcoraboeuf added a commit that referenced this issue Feb 5, 2017
dcoraboeuf added a commit that referenced this issue Feb 5, 2017
dcoraboeuf added a commit that referenced this issue Feb 5, 2017
dcoraboeuf added a commit that referenced this issue Mar 9, 2017
dcoraboeuf added a commit that referenced this issue Mar 10, 2017
dcoraboeuf added a commit that referenced this issue Mar 10, 2017
dcoraboeuf added a commit that referenced this issue Mar 10, 2017
dcoraboeuf added a commit that referenced this issue Mar 11, 2017
dcoraboeuf added a commit that referenced this issue Mar 12, 2017
dcoraboeuf added a commit that referenced this issue Mar 12, 2017
@dcoraboeuf dcoraboeuf removed the v4 Planned for version 4 label Apr 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant