-
Notifications
You must be signed in to change notification settings - Fork 76
Storing provenance in a Neo4j graph database
Storage in the Neo4j graph database can be activated using the SPADE controller. The default configuration is loaded from cfg/spade.storage.Neo4j.config
. Arguments provided when adding the storage with the SPADE controller override the defaults. The database
argument specifies the location in the filesystem where the Neo4j database will be created or accessed from:
-> add storage Neo4j database=spade.graph
Adding storage Neo4j... done
The database corresponding to the above command will be stored in lib/neo4j-community-4.1.1/spade.graph/
within SPADE's top-level directory.
Storage can be added and removed while the SPADE server is running. For example, this will cause the server to stop sending provenance records to the Neo4j database:
-> remove storage Neo4j
Shutting down storage Neo4j... done
This material is based upon work supported by the National Science Foundation under Grants OCI-0722068, IIS-1116414, and ACI-1547467. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation.
- Setting up SPADE
- Storing provenance
-
Collecting provenance
- Across the operating system
- Limiting collection to a part of the filesystem
- From an external application
- With compile-time instrumentation
- Using the reporting API
- Of transactions in the Bitcoin blockchain
- Filtering provenance
- Viewing provenance
-
Querying SPADE
- Illustrative example
- Transforming query responses
- Protecting query responses
- Miscellaneous