Added functional OrientDBDatabase, example data and config #179
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.
This can be tested by constructing a classpath with orient-commons, orientdb-core, orientdb-client,
orientdb-jdbc, orientdb-enterprise, and googlecode/concurrentlinkedhashmap-lru, along with
duke and lucene, creating an orient database using the countries-both-orient.create script,
and then running Duke with arguments
--noreindex --progress --showmatches ../../larsga/Duke/countries-orient.xml
The purpose of this example is to demonstrate using an already populated Database as both the
source of datasets to link and as the Duke database used to retrieve candidate matches.
One could additionally create a listener to insert edges into the same database, if one were so inclined.