Skip to main content

Alopex Python バインディング

Python から AlopexDB を操作するためのバインディングです。
Database/Transaction の基本機能に加え、ベクトル検索(numpy)と Unity Catalog 互換の Catalog API(polars)を提供します。

インストール

pip install alopex

Catalog API (polars) を使う場合:

pip install alopex[polars]

開発中は maturin を利用できます。

maturin develop -m crates/alopex-py/pyproject.toml

オプション依存:

  • numpy を使う場合: pip install alopex[numpy]
  • polars を使う場合: pip install alopex[polars]

対応バージョン

依存関係 対応バージョン
Python 3.8+
Polars 0.20+ (Catalog API)
NumPy 1.20+ (Vector API)

基本的な使い方

Database / Transaction

from alopex import Database, TxnMode

db = Database.new()

with db.begin(TxnMode.READ_WRITE) as txn:
    txn.put(b"user:1", b"alice")
    txn.commit()

with db.begin(TxnMode.READ_ONLY) as txn:
    value = txn.get(b"user:1")
    print(value)

db.close()

サーバー接続(v0.8.8)

alopex.connect(target) は接続先の指定だけで組み込み↔サーバーを切り替えます。 戻り値の形は両サーフェスで一致します(SELECT は列順を保った list[dict]、DML は int、DDL は None)。

import alopex

embedded = alopex.connect("/var/lib/alopex/db")            # 組み込み Database
remote = alopex.connect("https://127.0.0.1:8080",          # RemoteDatabase
                        api_key="secret")

for db in (embedded, remote):
    db.execute_sql("CREATE TABLE items (id INTEGER PRIMARY KEY, name TEXT)")
    db.execute_sql("INSERT INTO items (id, name) VALUES (?, ?)", [1, "alpha"])
    assert db.execute_sql("SELECT id, name FROM items") == [{"id": 1, "name": "alpha"}]

with remote.begin() as txn:          # サーバーセッション(/session/begin)
    txn.execute_sql("INSERT INTO items (id, name) VALUES (2, 'beta')")
    txn.commit()

remote.close()

組み込みDatabaseでは、繰り返し実行する1文をprepare()できます。bind indexは 1-basedで、?だけを受け付けます。

statement = embedded.prepare("INSERT INTO items (id, name) VALUES (?, ?)")
statement.bind(1, 2)
statement.bind(2, "beta")
statement.execute()
statement.reset()
statement.finalize()
target 結果
http://host:port / https://host:port RemoteDatabase
:memory:(既定) Database.open_in_memory()
file:///path/db / /path/db Database.open(path)
s3://bucket/prefix NotImplementedErrorALOPEX-PY204
その他 ValueErrorALOPEX-PY205

RemoteDatabase の主なオプション:

オプション 既定 説明
api_key None x-api-key ヘッダ。headersAuthorization: Bearer も可
timeout 60.0 サーバー既定 query_timeout(30s)の 2 倍。サーバー側の分類済みエラーを優先させる
sql_path / api_prefix URL の path 由来 /api/sql/query も同一ハンドラ
ssl_context None ssl.create_default_context() の差し替え(mTLS もここ)
insecure False 非 loopback への平文 http:// を許可する場合に必須
retries 0 接続確立の失敗だけを再試行。送信済みリクエストは絶対に再送しない
keep_alive / idle_reconnect_seconds True / 5.0 1 インスタンス 1 コネクション。並列実行はスレッドごとにインスタンスを作る

サーバーに等価物が無い操作は AttributeError ではなく理由付きの NotImplementedErrorcode == "ALOPEX-PY204")になります: execute_sql_stream / query_stream / flush / memory_usage / routing_diagnostics / thread_mode / HNSW 系 / トランザクションの KV・ベクトル系 / begin(TxnMode.READ_ONLY)cluster_status() は実装済みで、組み込みと同じ ClusterStatusSnapshot を返します。

エラーコードはサーバーの安定コード(UNAUTHORIZED / QUERY_TIMEOUT / SESSION_EXPIRED / ALOPEX-E### ほか)をそのまま AlopexError.code に載せ、 .correlation_id.http_status も付きます。例外型は両サーフェスで一致し、 実行中に起きるエラー(CAST 失敗 = ALOPEX-E004 など)は安定コードも一致します。 ただしパース・カタログ・型検査のエラーはサーバー側のルーティング前段で ALOPEX-E999 に潰れます(本来のコードはメッセージ内にのみ残る)。これは CLI の HTTP 経路でも同じサーバー側の既知の問題で、詳細と追跡は docs/python-server-client.md の D20 を参照してください。クライアント固有は ALOPEX-PY201(接続失敗)/ ALOPEX-PY202(タイムアウト)/ ALOPEX-PY203 (プロトコル違反)/ ALOPEX-PY204(サーバーに等価物なし)/ ALOPEX-PY205 (不正な接続先・オプション)の 5 つです。閉じたハンドルの操作は組み込みと同じ AlopexError("database is closed") + ALOPEX-PY999 です。

サーバーセッションはサーバーの session_ttl(既定 300 秒)で失効し、 SESSION_EXPIRED として観測されます(組み込みトランザクションには TTL がありません)。

詳細は docs/python-server-client.md を参照してください。

v0.8 embedded-local stream / DataFrame API

v0.8 の stream API は embedded-local database 専用です。remote session(サーバー セッション)は RemoteDatabase.begin() で利用できますが、stream・remote DataFrame execution は引き続き提供しません(サーバーの JSONL ストリームは列名 メタデータを持たないため、組み込みの dict yield 契約を満たせません)。Database は既定で thread_mode="multi" であり、 thread_mode="single" を選ぶと database、transaction、stream、DataFrame、LazyFrame は作成した Python thread だけで使用できます。

同期 SQL / scan stream

execute_sql_stream() は、単一 table の local SELECT、row-local WHERE、projection、LIMIT / OFFSET の documented subset を一行ずつ返します。query_stream()LocalScan.tablecsvparquetcolumnar_segmentlazyframe の五つだけを受け取ります。非対応 SQL、callback、remote source は stream を開く前に AlopexError となります。

from alopex import Database, LocalScan

db = Database.new()
db.execute_sql("CREATE TABLE users (id INTEGER PRIMARY KEY, name TEXT)")
db.execute_sql("INSERT INTO users (id, name) VALUES (1, 'one'), (2, 'two')")

with db.execute_sql_stream(
    "SELECT id, name FROM users WHERE id >= 1",
    resource_limit_bytes=64 * 1024 * 1024,
    timeout=5.0,
) as stream:
    for row in stream:
        print(row)
    print(stream.status)
    # {"terminal": "exhausted", "rows_delivered": 2,
    #  "resource_limit_bytes": ..., "resource_scope": "sql_row",
    #  "transaction_effect": "none"}

DataFrameStream.status は同じ構造で、rows_delivered の代わりに batches_deliveredresource_scope="dataframe_batch" を返します。normal exhaustion は以後 end-of-stream、close/cancel/timeout/failure は以後も同じ識別可能な terminal error を返します。

transaction 内の stream は暗黙 commit しません。正常に exhaustion した read stream は commit 可能であり、 early close、cancel、failure は transaction.status["stream_effect"] と stream の transaction_effect で確認した後に rollback してください。active stream 中の commit は拒否されます。

Python DataFrame streaming / expressions

LazyFrame.collect_batches() は Phase 3 と同じ source、row order、schema、NULL、resource contract で有限 DataFrame batch を返します。concatconcat_strselectfilterwith_columns は同じ expression semantics を使用します。

from alopex import DataFrame, col, concat_str, lit

plan = (
    DataFrame({"id": [1, 2, 3], "left": ["a", "b", "c"], "right": ["x", "y", "z"]})
    .lazy()
    .filter(col("id").gt(lit(1)))
    .select([
        col("id").add(lit(10)).alias("next_id"),
        concat_str([col("left"), col("right")], "-").alias("label"),
    ])
)

with plan.collect_batches(chunk_size=1) as batches:
    for batch in batches:
        print(batch.to_dict(as_series=False))

asyncio

alopex.asyncio は Python 3.8 以上の標準 asyncio loop をサポートし、caller に Rust/Tokio runtime を 要求しません。prefetch_batches は read ahead の上限、max_buffered_batches は ready result buffer の上限です。両者は 0 <= prefetch_batches <= max_buffered_batches、かつ max_buffered_batches >= 1 でなければなりません。consumer_idle_timeouttimeout の単位は秒です。 native worker は bounded Rust payload だけを保持し、Python の row / DataFrame 変換は asyncio consumer 側で 行われます。Python の producer queue や callback は使用しません。

import asyncio
from alopex.asyncio import AsyncDatabase

async def main() -> None:
    async with await AsyncDatabase.new() as db:
        await db.execute_sql("CREATE TABLE events (id INTEGER PRIMARY KEY)")
        await db.execute_sql("INSERT INTO events (id) VALUES (1), (2)")
        stream = await db.execute_sql_stream(
            "SELECT id FROM events",
            prefetch_batches=1,
            max_buffered_batches=1,
            consumer_idle_timeout=5.0,
        )
        async with stream:
            async for row in stream:
                print(row)

asyncio.run(main())

同じ stream で同時に二つの anext() を実行すると stream_busy です。task cancellation、aclose()cancel()、idle timeout は stream の native source を終端させ、後続の独立した database operation を継続できます。

ベクトル検索(numpy 必須)

import numpy as np
from alopex import Database, Metric, TxnMode

db = Database.new()
with db.begin(TxnMode.READ_WRITE) as txn:
    vec = np.array([1.0, 0.0, 0.0], dtype=np.float32)
    txn.upsert_vector(b"k1", None, vec, Metric.COSINE)
    results = txn.search_similar(vec, Metric.COSINE, 1, return_vectors=True)
    print(results[0].key, results[0].score)
    if results[0].vector is not None:
        print(results[0].vector.dtype, results[0].vector.shape)

NumPy 入出力とゼロコピー条件(v0.3.5)

入力(Python → Rust):

  • dtype: float32 が優先。float64float32 に変換して処理します。
  • layout: C-contiguous が優先。非連続(strided/Fortran order 等)は C-contiguous に変換して処理します。
  • ゼロコピー入力: float32 かつ C-contiguous の場合は Rust 側でコピーなしに参照します。

出力(Rust → Python):

  • Transaction.search_similar(..., return_vectors=True) の場合、SearchResult.vectornumpy.ndarray[float32] を含められます。
  • Transaction.search_similar(..., zero_copy_return=True) / Transaction.get_vector(..., zero_copy_return=True) の場合、可能なら所有権移譲によるゼロコピー返却を行います(False の場合はコピー)。

GIL:

  • upsert_vector / search_similar / search_hnsw は重い処理中に GIL を解放します。

HNSW インデックス(numpy 必須)

import numpy as np
from alopex import Database, HnswConfig, TxnMode

db = Database.new()
db.create_hnsw_index("idx", HnswConfig(2))

with db.begin(TxnMode.READ_WRITE) as txn:
    vec = np.array([1.0, 0.0], dtype=np.float32)
    txn.upsert_to_hnsw("idx", b"k1", vec, None)
    txn.commit()

results, stats = db.search_hnsw("idx", np.array([1.0, 0.0], dtype=np.float32), 1)
print(stats.nodes_visited, stats.distance_computations, stats.search_time_us)

Catalog API(polars 必須)

import polars as pl
from alopex import Catalog, ColumnInfo

Catalog.create_catalog("main")
Catalog.create_namespace("main", "default")

columns = [ColumnInfo("id", "int", 0, False)]
Catalog.create_table("main", "default", "users", columns, "/tmp/users.parquet")

df = pl.DataFrame({"id": [1, 2], "name": ["a", "b"]})
Catalog.write_table(
    df,
    "main",
    "default",
    "users",
    delta_mode="overwrite",
    storage_location="/tmp/users.parquet",
)

lazy_frame = Catalog.scan_table("main", "default", "users")
print(lazy_frame.collect())

注意事項

  • numpy / polars が未インストールの場合、対応 API は AlopexError を返します。
  • Phase 1 では Parquet のみ対応しています。

Release files for alopex 0.8.11

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

Source distribution (sdist)

Source distribution for alopex 0.8.11
File Size Uploaded
alopex-0.8.11.tar.gz 1.4 MB Details

Built distributions (wheels)

Table of built distributions (wheels) for alopex 0.8.11
File
alopex-0.8.11-cp38-abi3-win_amd64.whl CPython 3.8 abi3 Windows x86-64 Details
alopex-0.8.11-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl CPython 3.8 abi3 Linux glibc 2.17+ x86-64 Details
alopex-0.8.11-cp38-abi3-macosx_11_0_arm64.whl CPython 3.8 abi3 macOS 11.0+ ARM64 Details
alopex-0.8.11-cp38-abi3-macosx_10_12_x86_64.whl CPython 3.8 abi3 macOS 10.12+ x86-64 Details

Total release size:41.0 MB

Release files / alopex-0.8.11.tar.gz

Download URL alopex-0.8.11.tar.gz
Size 1.4 MB
Tags Source
SHA-256 checksum
How to use checksums
ae9c10a2e664996de45ff9c0e0e821a0730166c69e21ad74487f01fbe46559d3
BLAKE2b-256 checksum
How to use checksums
6571661b78a2e1786f23a297fa474a6383edbac22eb2da8f29a30d0773a28b5a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / alopex-0.8.11-cp38-abi3-win_amd64.whl

Download URL alopex-0.8.11-cp38-abi3-win_amd64.whl
Size 10.3 MB
Tags CPython 3.8 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
e862e3e2c73e05d33de78d069c71ad5253b97926bc0419c703e9695b2cc8d3ee
BLAKE2b-256 checksum
How to use checksums
a49d9fd977c8584f73382455f2e9cc65cf7886a05447ed348708bef4fbdcbc83
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / alopex-0.8.11-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl

Download URL alopex-0.8.11-cp38-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
Size 10.3 MB
Tags CPython 3.8 Linux glibc 2.17+ x86-64 abi3
SHA-256 checksum
How to use checksums
55c818a8f8ee301f898c2ed73b45af99e70bd98e35c64339fdc3bc4285e17fa5
BLAKE2b-256 checksum
How to use checksums
4bb87ac90c01013117dabe1ad3afbe12ce1c5f4f2abd871904cc1493d3635e47
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / alopex-0.8.11-cp38-abi3-macosx_11_0_arm64.whl

Download URL alopex-0.8.11-cp38-abi3-macosx_11_0_arm64.whl
Size 9.2 MB
Tags CPython 3.8 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
f786315c664af95a6231d09075f02c9d6380adbf3a1ad7f7dcb2236863184cd1
BLAKE2b-256 checksum
How to use checksums
8dd956f846ee5666b37770ba1ae1b9c4bfd5d93d447ad7f46e2e0a282f4398e7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / alopex-0.8.11-cp38-abi3-macosx_10_12_x86_64.whl

Download URL alopex-0.8.11-cp38-abi3-macosx_10_12_x86_64.whl
Size 9.8 MB
Tags CPython 3.8 abi3 macOS 10.12+ x86-64
SHA-256 checksum
How to use checksums
0797938c07e11fb83f09bf2183791758a294ad2353e3878171820cf56bff3384
BLAKE2b-256 checksum
How to use checksums
8cdbe9cf0b2e245e9a37dcd5f116f7497166808b463ca412a5b7a7bba73876f9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.13

5 release files

0.8.12

5 release files

This release

0.8.11 This release

5 release files

0.8.10

5 release files

0.8.9

5 release files

0.8.8

5 release files

0.8.7

5 release files

0.8.6

5 release files

0.8.5

5 release files

0.8.4

5 release files

0.8.3

5 release files

0.8.2

5 release files

0.8.1

5 release files

0.8.0

5 release files

0.7.7

5 release files

0.7.6

5 release files

0.7.5

5 release files

0.7.4

5 release files

0.7.3

5 release files

0.7.2

5 release files

0.7.1

5 release files

0.7.0

5 release files

0.6.0

5 release files

0.4.0

8 release files

0.3.5

8 release files

0.3.3

8 release files

0.3.2

8 release files

0.3.1

8 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page