Storing provenance

Raza Ahmad edited this page Jul 12, 2018 · 5 revisions

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.)

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.