-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat: Add scripts to enbale neo4j persistance after tao install #3907
Conversation
5d03162
to
0ca4070
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #3907 +/- ##
==========================================
Coverage 27.55% 27.55%
Complexity 10976 10976
==========================================
Files 922 922
Lines 33910 33910
==========================================
Hits 9345 9345
Misses 24565 24565 ☔ View full report in Codecov by Sentry. |
0ca4070
to
fd462e0
Compare
fd462e0
to
403457a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Checklist
- Tests are running successfully (old and new ones) on my local machine (if applicable)
- New code respects code style rules
- New code respects best practices
- New code is not subject to concurrency issues (if applicable)
- Feature is working correctly on my local machine (if applicable)
- Acceptance criteria are respected
- Pull request title and description are meaningful
- Pull request's target is not
master
- Commits are following conventional commits
- Commits messages are meaningful
- Commits are atomic
->getPersistenceById($persistenceId); | ||
|
||
$persistence->run('MATCH (n) DETACH DELETE n'); | ||
$persistence->run('CALL apoc.schema.assert({}, {}, true) YIELD label, key RETURN *'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: It is not clear to me what is the purpose of this call, as we do not check results after it, could you clarify?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It removes all constraints
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for clarifying that. Just a note (it is not a big deal), I think YIELD
and RETURN
sections are not required here as we do not use function results after execution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works good, would also remove SmoothModel dependency 👍🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me now.
38bcfc5
to
31bf921
Compare
31bf921
to
a5cdf12
Compare
Version
There are 0 BREAKING CHANGE, 2 features, 1 fix |
Ticket - https://oat-sa.atlassian.net/browse/REL-1294
In order to setup neo4j ontology persistence right after tao installation I propose to use already existing migration script with some additional scripts for setup. As long we are going to support sql database along with neo4j this approach has to be valid and allow us to move forward.
How to test:
composer.json
andseed.json
(only postInstall scripts can be borrowed) files providedtaoDockerize install
to install taoseed.json
file which I used to install tao:composer.json
I used: