3.7. Storage#
3.7.1. Description#
The Storage is an object that is responsible for storing extracted features as computed from Marker
step of the pipeline. If the pipeline is provided with a storage-like object, the extracted features are stored via
that object else they are kept in memory.
Storage is meant to be used inside the datagrabber context but you can operate on them outside the context as long as the processed data is in the memory and the Python runtime has not garbage-collected it.
The Markers are responsible for defining what storage kind (matrix, table, timeseries)
they support for which data type by overriding its store method. The storage object in turn
declares and provides implementation for specific storage kind. For example, junifer.storage.SQLiteFeatureStorage
supports saving matrix, table and timeseries via store_matrix, store_table and store_timeseries
methods respectively.
For storage interfaces not supported by junifer yet, you can either make your own Storage by providing a concrete
implementation of junifer.storage.BaseFeatureStorage or open an issue on junifer Github and we can help you out.
3.7.2. Currently supported storage types#
Storage Type |
Description |
Options |
Reference |
|---|---|---|---|
|
A 2D matrix with row and column names |
|
|
|
A vector of values with column names |
|
|
|
A 2D matrix of values with column names |
|
3.7.3. Currently supported storage interfaces#
Storage class |
File extension |
File type |
Storage kinds |
|---|---|---|---|
|
SQLite |
|