ApertureDB Python SDK

The ApertureDB Python SDK provides a seamless interface for interacting with ApertureDB, the purpose-built database for storing, managing, and querying visual data (images, videos) alongside metadata, embeddings, and annotations.

This SDK includes comprehensive utilities to efficiently ingest and retrieve data, manage graph-based metadata, perform similarity searches on embeddings, and seamlessly integrate with the broader ML/AI ecosystem.

🚀 Integrations & Capabilities

The SDK is designed for modern ML workflows and offers seamless integrations with (some require additional dependencies):

Deep Learning Frameworks: Seamless conversion of ApertureDB queries into PyTorch (PyTorchDataset.ApertureDBDataset) and TensorFlow (ApertureDBTensorFlowDataset) data loaders for immediate model training.
Vector Search & Embeddings: First-class support for storing and retrieving high-dimensional descriptors, including native embedding extraction utilizing CLIP (requires openai-clip) and Facenet.
Distributed Data Processing: Integration with Dask to handle parallelized data loading and large-scale query execution.
Cloud Storage Integrations: Easy handling of assets stored remotely using Boto3 (AWS S3) and Google Cloud Storage.
ML Croissant: Native parsing and handling of datasets aligned with the ML Croissant metadata format (requires mlcroissant).
Knowledge Graphs: Ability to execute and map SPARQL queries natively into the database (requires rdflib).

📦 Installation

To install the SDK in a standard virtual environment with all core integrations (such as PyTorch and TensorFlow support):

pip install "aperturedb[complete]"

To install just the base client without optional deep learning extras:

pip install aperturedb

📚 Documentation & Examples

🛠 Development Setup

The recommended way to contribute is to clone this repository and perform an editable installation:

git clone https://github.com/aperture-data/aperturedb-python.git
cd aperturedb-python
pip install -e '.[dev]'

🧪 Running Tests

The tests are located inside the test/ directory. They are designed to run within an isolated Linux container network composed of aperturedb, lenz, nginx, ca, and webui.

If you'd like to bring up the environment manually, ensure your working directory is test/ and run:

docker compose up -d

Development Environment Adjustments

To connect to the local test environment natively from your host, edit test/dbinfo.py to match the exposed ports (you can find the ephemeral ports by running docker compose port lenz 55551 and docker compose port nginx 443):

DB_TCP_HOST = 'localhost'
DB_REST_HOST = 'localhost'
DB_TCP_PORT  = 0  # Replace with the mapped host port for lenz
DB_REST_PORT = 0  # Replace with the mapped host port for nginx 443
# VERIFY_HOSTNAME = False # Optional: Only required if connecting via IP instead of localhost

Executing Tests

To run the entire test suite, export the necessary credentials and execute the test runner script:

export GCP_SERVICE_ACCOUNT_KEY=<content of a GCP SERVICE ACCOUNT JSON file>
bash run_test.sh

To run a specific test file natively via pytest:

PROJECT=aperturedata KAGGLE_username=ci KAGGLE_key=dummy coverage run -m pytest test_Session.py -v -s --log-cli-level=DEBUG

(Note: The test suite assumes a Linux x86_64 environment. Adjustments may be required for macOS or Windows.)

⚙️ Runtime Configuration Variables

The following environment variables can modify the runtime behavior of the SDK, which is particularly useful for debugging:

Variable	Type	Description	Default Value
`ADB_DEBUGGABLE`	`flag`	If set (to any value), allows the application to register a fault handler that dumps a trace when `SIGUSR1` is sent to the process.	Not set
`LOG_FILE_LEVEL`	`string`	The threshold for emitting log messages into the `error<timestamp>.log` file.	`WARN`
`LOG_CONSOLE_LEVEL`	`string`	The threshold for emitting log messages to `stdout`.	`ERROR`
`ADB_LOG_FILE`	`string`	Custom file path for the log output.	Not set

🐞 Bug Reports & Contributing

Bugs: Please report any issues regarding functionality, documentation, or tests by creating a GitHub Issue.
Contributing: We welcome Pull Requests! When submitting a PR, include a brief description of the problem and the implemented fix.
Coding Standards: Our CI enforces coding style guidelines using autopep8 and trailing whitespace checks. If a PR encounters failures, review the CI logs for details on the offending lines.

Metadata

Release files for aperturedb 0.5.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aperturedb 0.5.1
File	Size	Uploaded
aperturedb-0.5.1.tar.gz	167.5 kB	Oct 12, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for aperturedb 0.5.1
File	Interpreter	ABI	Platform	Reset
aperturedb-0.5.1-py3-none-any.whl 165.5 kB Oct 12, 2026	Python 3	none	any	Details

Total release size: 333.0 kB

Release files / aperturedb-0.5.1.tar.gz

Download URL	aperturedb-0.5.1.tar.gz
Size	167.5 kB
Tags	Source
SHA-256 checksum How to use checksums	`5bab33414744d5df558a5d6ea5e9c9f4a1f0a051c6ca1a81405fa9663d7937db`
BLAKE2b-256 checksum How to use checksums	`64f4946996412b7def4b966d69bfe09656379140472a4bc69712c84ddf9f4ddc`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.10.22`

Release files / aperturedb-0.5.1-py3-none-any.whl

Download URL	aperturedb-0.5.1-py3-none-any.whl
Size	165.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`1cb3f7bfb5d68a0ccab25c286ad35ea347db21df76e36e07ab9996cadc159a91`
BLAKE2b-256 checksum How to use checksums	`f332b3c8f338c80cf58895c626ca862590121595648121822e47ac4c7a776845`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.10.22`