This is python library for Lightblue database. It can be used as API interface.
Levels of abstraction (from low to high):
Basic modules to query a LightBlue on a level of the request.
from lightblue.service import LightBlueService
from lightblue.entity import LightBlueEntity
service = LightBlueService(
'https://data-url.com/data',
'https://metadata-url.com/metadata')
interface = LightBlueEntity(
lightblue_service=service,
entity_name='foo',
version='1.0.0')
Class that represents a query to LB in time (both non-executed and executed states). Has a relation to the LightBlueEntity.
Usage example:
from lightblue.query import LightBlueQuery
LightBlueQuery(_id='hash', interface=interface).find()
a = LightBlueQuery(('foo', '$neq', 'value'), bar='value2', interface=interface)
a._add_to_projection('foo', recursive=['bar'])
a._add_to_update(unset='foobar')
a.update()
LightBlueQuery.insert({'key': 'item'}, interface)
Why _add_to_projection() is private? Because we have another level of abstraction...
- inherits LightBlueQuery and extends the functionality with post-processing, so you can call:
from lightblue.selection import LightBlueGenericSelection
LightBlueGenericSelection(foo='value', interface=interface).find(
check_response=True,
selector='/processed/0/bar/',
count=(1, 2),
fallback=None,
postprocess=lambda x: x.split('.')[-1])
so the query above will select documents with a specific foo value, it will check the successful query of a LB response and count of response documents of min 1 and max 2, with a fallback if it is out of range. It will select 'bar' from the first response item and will process it with the provided lambda.
That level of abstraction is generic because it is not specific to an entity.