maggma
maggma copied to clipboard
MongoDB aggregation machine
Merge these two stores into one as the 2nd is just an init interface.
To avoid using hidden attribute `store._collection.aggregate` Alternatively, perhaps a `pipeline` kwarg instead on `query`
Vault has done a lot upgrade it's capabilities since the vault store was first created. It would be nice to rebuild our VaultStore so that we can replace mongogrant with...
For some reason running a builder in jupyter causes duplicate messages to print
the behavior of `Store.update` should be modified to return the keys for the docs it was able to successfully update.
`MSONable` is great but has a couple flaws: - support pydantic `BaseModel` for defining the data model - better handling of serializing components - Better encapsulation of serialization methods. This...
Add the ability to include custom reporting from builders for reporting store
The MongoStore does not provide an `insert` option, only an `update` option. This does a `bulk_write` but as a list of `ReplaceOne` due to how maggma deals with key handling,...
Add MinIO to the github actions tests and run full integration tests against this
Considering attaching validators to builder instead of store, i.e. a `doc_validator`, initially only in `MapBuilder`, would be called inside `MapBuilder`'s `process_item` and `schema` then added as a kwarg to the...