[WIP] Extractor database #35
Open
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
PROxZIMA
added
documentation
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.
Description
A database manager for the
Crawlerand theExtractormodules. Neo4j is the most suitable candidate of all as it's fast, scalable and is capable of storing huge amount of data; that too in graphical manner. This makes it easier to understand and manipulate as per our need.Motivation and Context
The goal is to use a unified platform to store all the information for both crawler and extractor. Fixes #32
How Has This Been Tested?
TODO
Screenshots (if appropriate):
Neo4j database for depth 1 crawl
Some logs
Types of changes
Checklist: