-
Notifications
You must be signed in to change notification settings - Fork 71
Storing provenance
If no storage is added, the SPADE server will silently discard any provenance metadata that is sent to it. To subsequently use the information, it must be committed to persistent storage. An arbitrary number of storage subsystems can be added. The SPADE server will send the filtered, integrated provenance metadata to each of the storage classes that have been added.
SPADE includes support for storing provenance in a graph database (Neo4j), relational databases (H2, MySQL, PostgreSQL), and in Graphviz format. (Support for other storage can be implemented creating a class in the spade.storage.* package that extends the spade.core.AbstractStorage class.)
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