Update example default triple store from SDB to TDB #144
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gneissone
previously approved these changes
Feb 24, 2020
There was a problem hiding this comment.
Approving per discussion among committers and community response to the VIVO Triple Store Roadmap Proposal.
Only comment is I would suggest commenting out the SQL database connection settings in example.runtime.properties to avoid confusion.
|
@gneissone : updated per comment. |
I don't think the commit was pushed, I don't see any difference. |
gneissone
approved these changes
Feb 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: https://jira.lyrasis.org/browse/VIVO-1741
What does this pull request do?
No functional changes.
This pull-request updates the example.applicationSetup.n3 file to reference a TDB triple store by default (instead of SDB).
Note: Support for SDB still exists.
How should this be tested?
Use the example.applicationSetup.n3 configuration in a new VIVO installation.
Verify that VIVO works as expected.
Verify that content is created in the TDB "hasTdbDirectory" location.
Interested parties
@VIVO-project/vivo-committers