ApexBase
High-performance HTAP embedded database with Rust core and Python API
ApexBase is an embedded columnar database designed for Hybrid Transactional/Analytical Processing (HTAP) workloads. It combines a high-throughput columnar storage engine written in Rust with an ergonomic Python API, delivering analytical query performance that surpasses DuckDB and SQLite on most benchmarks — all in a single .apex file with zero external dependencies.
Table of Contents
- Features
- Installation
- Quick Start
- Usage Guide
- Performance
- Server Protocols
- PostgreSQL Wire Protocol Server
- Arrow Flight gRPC Server
- Rust Native API
- Architecture
- API Reference
- Documentation
- License
Features
- HTAP architecture — V4 Row Group columnar storage with DeltaStore for cell-level updates; fast inserts and fast analytical scans in one engine
- Multi-database support — multiple isolated databases in one directory; cross-database queries with standard
db.tableSQL syntax - Single-file storage — custom
.apexformat per table, no server process, no external dependencies - Comprehensive SQL — DDL, DML, JOINs (INNER/LEFT/RIGHT/FULL/CROSS), subqueries (IN/EXISTS/scalar), CTEs (WITH ... AS), UNION/UNION ALL/INTERSECT/EXCEPT, window functions, EXPLAIN/ANALYZE, multi-statement execution
- 70+ built-in functions — math (ABS, SQRT, POWER, LOG, trig), string (UPPER, LOWER, SUBSTR, REPLACE, CONCAT, REGEXP_REPLACE, ...), date (YEAR, MONTH, DAY, DATEDIFF, DATE_ADD, ...), conditional (COALESCE, IFNULL, NULLIF, CASE WHEN, GREATEST, LEAST)
- Aggregation and analytics — COUNT, SUM, AVG, MIN, MAX, COUNT(DISTINCT), GROUP BY, HAVING, ORDER BY with NULLS FIRST/LAST
- Window functions — ROW_NUMBER, RANK, DENSE_RANK, NTILE, PERCENT_RANK, CUME_DIST, LAG, LEAD, FIRST_VALUE, LAST_VALUE, NTH_VALUE, RUNNING_SUM, and windowed SUM/AVG/COUNT/MIN/MAX with PARTITION BY and ORDER BY
- Transactions — BEGIN / COMMIT / ROLLBACK with OCC (Optimistic Concurrency Control), SAVEPOINT / ROLLBACK TO / RELEASE, statement-level auto-rollback
- MVCC — multi-version concurrency control with snapshot isolation, version store, and garbage collection
- Indexing — B-Tree and Hash indexes with CREATE INDEX / DROP INDEX / REINDEX; automatic multi-index AND intersection for compound predicates
- Full-text search — built-in NanoFTS integration with fuzzy matching
- Vector search — SIMD-accelerated nearest-neighbour search with 6 distance metrics (L2, cosine, dot, L1, L∞, L2²); heap-based O(n log k) TopK; single-query
topk_distance()and batchbatch_topk_distance()Python APIs; SQLexplode_rename(topk_distance(...))syntax; 3–4× faster than DuckDB at 1M rows - Float16 vector storage —
FLOAT16_VECTORcolumn type stores embeddings as 16-bit floats (half the memory of float32); SIMD-accelerated f16 distance kernels via NEON fp16 on ARM (FCVTL/FCVTL2) and AVX2+F16C on x86_64; automatic runtime CPU dispatch; ≥2× faster than f32 on Apple Silicon; transparent API — query with float32, stored as f16 - JIT compilation — Cranelift-based JIT for predicate evaluation and SIMD-vectorized aggregations
- Zero-copy Python bridge — Arrow IPC between Rust and Python; direct conversion to Pandas, Polars, and PyArrow
- Durability levels — configurable
fast/safe/maxwith WAL support and crash recovery - Compact storage — dictionary encoding for low-cardinality strings, LZ4 and Zstd compression
- File reading table functions —
read_csv(),read_parquet(),read_json()directly in SQLFROMclauses; parallel mmap parsing; full SQL (WHERE / GROUP BY / JOIN / UNION) on top of any file - Parquet interop — COPY TO / COPY FROM Parquet files
- PostgreSQL wire protocol — built-in server for DBeaver, psql, DataGrip, pgAdmin, Navicat, and any PostgreSQL-compatible client; two distribution modes (Python CLI or standalone Rust binary)
- Arrow Flight gRPC server — high-performance columnar data transfer over HTTP/2; streams Arrow IPC RecordBatch directly, 4–7× faster than PG wire for large result sets; accessible via
pyarrow.flight, Go arrow, Java arrow, and any Arrow Flight client - Cross-platform — Linux, macOS, and Windows; x86_64 and ARM64; Python 3.9 -- 3.13
Installation
Build from source (requires Rust toolchain):
Quick Start
# Open (or create) a database directory
=
# Create a table
# Store records
# SQL query
=
# Convert to DataFrame
=
Usage Guide
Database Management
ApexBase supports multiple isolated databases within a single root directory. Each named database lives in its own subdirectory; the default database uses the root directory.
# Switch to a named database (creates it if needed)
# Combined: switch database + select/create a table in one call
# List all databases
= # ["analytics", "default", "hr"]
# Current database
# "analytics"
# Cross-database SQL — standard db.table syntax
All SQL operations (SELECT, INSERT, UPDATE, DELETE, JOIN, CREATE TABLE, DROP TABLE, ALTER TABLE) support database.table qualified names, allowing cross-database queries in a single statement.
Table Management
Each table is stored as a separate .apex file. Tables must be created before use.
# Create with optional schema
# Switch tables
# List / drop
=
Data Ingestion
# Columnar dict (fastest for bulk data)
# From pandas / polars / PyArrow (auto-creates table when table_name given)
SQL
ApexBase supports a broad SQL dialect. Examples:
# DDL
# DML
# SELECT with full clause support
# JOINs
# Subqueries
# CTEs
# Window functions
# Set operations
# Multi-statement
# INSERT ... ON CONFLICT (upsert)
# CREATE TABLE AS
# EXPLAIN / EXPLAIN ANALYZE
# Parquet interop
File Reading Table Functions
Read external files directly in a SQL FROM clause — no import step required. The full SQL engine runs on top: WHERE, GROUP BY, ORDER BY, JOIN, UNION, etc.
# CSV: schema inferred automatically, parallel mmap parser
=
# TSV — specify delimiter
=
# No header row
=
# Parquet: schema from file metadata, parallel column decode
=
# JSON / NDJSON: auto-detects format (NDJSON or pandas column-oriented)
=
# Full SQL on top of a file
=
# JOIN a file with a stored table
=
# EXCEPT using a file as a blocklist
=
| Function | Options | Description |
|---|---|---|
read_csv(path) |
header=true, delimiter=',' |
Read CSV/TSV; auto-infers schema |
read_parquet(path) |
— | Read Parquet; schema from file metadata |
read_json(path) |
— | Read NDJSON or pandas JSON; auto-detects format |
See docs/API_REFERENCE.md for full details.
Transactions
# undo Tx2 only
# Tx1 persisted
Transactions use OCC validation — concurrent writes are detected at commit time.
Indexes
# Queries automatically use indexes when applicable
# index scan
Full-Text Search
ApexBase ships a native full-text search engine (NanoFTS) integrated directly into the SQL executor. FTS is available through all interfaces — Python API, PostgreSQL Wire, and Arrow Flight — without any Python-side middleware.
SQL interface (recommended)
# 1. Create the FTS index via SQL DDL
# Optional: specify lazy loading and cache size
# 2. Query using MATCH() / FUZZY_MATCH() in WHERE
=
=
# Combine with other predicates
=
# FTS also works in aggregations
=
# Manage indexes
# list all FTS-enabled tables
# disable, keep files
# remove index + delete files
Python API (alternative)
# Initialize FTS for current table
# Search
=
= # tolerates typos
=
=
# Lifecycle
# suspend without deleting files
# remove index + delete files
Tip: The SQL interface (
MATCH()/FUZZY_MATCH()) works over PG Wire and Arrow Flight without any extra setup; the Python API methods are Python-process-only.
Vector Search
ApexBase provides SIMD-accelerated nearest-neighbour search with a zero-copy mmap scan buffer. Supports 6 distance metrics and both single-query and batch modes.
# Store vectors — numpy arrays are stored as FixedList columns (optimal)
=
# Single-query: returns ResultView with _id and dist columns
=
= # columns: _id, dist
= # numpy int64 array
= # full records
# Custom metric and column names
=
# Batch: N queries in one Rust call (scan_buf loaded once, Rayon parallel)
=
=
# result.shape == (100, 10, 2)
= # (100, 10)
= # (100, 10)
# SQL: explode_rename(topk_distance(...)) — same query, SQL form
=
Supported metrics: 'l2' / 'euclidean', 'l2_squared', 'l1' / 'manhattan', 'linf' / 'chebyshev', 'cosine' / 'cosine_distance', 'dot' / 'inner_product'
Benchmark (1M rows × dim=128, k=10):
| Metric | ApexBase | DuckDB | Speedup |
|---|---|---|---|
| L2 | ~12ms | ~47ms | 3.8× faster |
| Cosine | ~13ms | ~42ms | 3.1× faster |
| Dot | ~13ms | ~36ms | 2.8× faster |
See docs/API_REFERENCE.md#vector-search for full details.
Record-Level Operations
= # by internal _id
=
=
Column Operations
# "Int64"
# ["name", "age", "city"]
ResultView
Query results are returned as ResultView objects with multiple output formats:
=
= # pandas DataFrame (zero-copy by default)
= # polars DataFrame
= # PyArrow Table
= # list of dicts
# (rows, columns)
# column names
# row count
# first row as dict
# single value (for aggregates)
# numpy array of _id values
Context Manager
# Automatically closed on exit
Performance
ApexBase vs SQLite vs DuckDB (1M rows)
Three-way comparison on macOS 26.3, Apple arm (10 cores), 32 GB RAM. Python 3.11.10, ApexBase v1.9.0, SQLite v3.45.3, DuckDB v1.1.3, PyArrow v23.0.1.
Dataset: 1,000,000 rows × 5 columns (name, age, score, city, category). Average of 5 timed iterations after 2 warmup runs.
| Query | ApexBase | SQLite | DuckDB | vs Best Other |
|---|---|---|---|---|
| Bulk Insert (1M rows) | 332.72ms | 1.02s | 177.42s | 3.1x faster |
| COUNT(*) | 0.065ms | 8.63ms | 0.513ms | 7.9x faster |
| SELECT * LIMIT 100 [cold] | 0.032ms | 0.067ms | 0.224ms | 2.1x faster |
| SELECT * LIMIT 100 [warm] | 0.028ms | 0.066ms | 0.242ms | 2.4x faster |
| SELECT * LIMIT 10K [cold] | 0.780ms | 6.76ms | 4.50ms | 5.8x faster |
| SELECT * LIMIT 10K [warm] | 0.806ms | 6.79ms | 4.56ms | 5.7x faster |
| Filter (name = 'user_5000') | 0.203ms | 40.98ms | 1.69ms | 8.3x faster |
| Filter (age BETWEEN 25 AND 35) | 22.60ms | 175.84ms | 89.60ms | 4.0x faster |
| GROUP BY city (10 groups) | 1.42ms | 365.70ms | 3.20ms | 2.3x faster |
| GROUP BY + HAVING | 1.44ms | 364.48ms | 3.00ms | 2.1x faster |
| ORDER BY score LIMIT 100 | 1.81ms | 51.77ms | 4.68ms | 2.6x faster |
| Aggregation (5 funcs) | 0.220ms | 85.41ms | 1.16ms | 5.3x faster |
| Complex (Filter+Group+Order) | 1.25ms | 199.84ms | 2.74ms | 2.2x faster |
| Point Lookup (by _id) | 0.024ms | 0.046ms | 2.85ms | 1.9x faster |
| Retrieve Many (100 IDs) | 0.190ms | 0.419ms | 4.68ms | 2.2x faster |
| Insert 1K rows | 0.664ms | 1.35ms | 163.67ms | 2.0x faster |
| SELECT * → pandas (full scan) | 82.39ms | 1.18s | 198.81ms | 2.4x faster |
| GROUP BY city, category (100 grp) | 3.96ms | 691.08ms | 6.16ms | 1.6x faster |
| LIKE filter (name LIKE 'user_1%') | 21.38ms | 130.91ms | 53.18ms | 2.5x faster |
| Multi-cond (age>30 AND score>50) | 47.24ms | 343.33ms | 192.97ms | 4.1x faster |
| ORDER BY city, score DESC LIMIT 100 | 3.11ms | 70.36ms | 7.68ms | 2.5x faster |
| COUNT(DISTINCT city) | 0.686ms | 90.60ms | 4.77ms | 7.0x faster |
| IN filter (city IN 3 cities) | 31.91ms | 310.84ms | 152.20ms | 4.8x faster |
| UPDATE rows (age = 25) | 7.75ms | 38.45ms | 14.46ms | 1.9x faster |
| Store+DELETE 1K (combined) | 0.849ms | 35.25ms | 176.53ms | 41.5x faster |
| DELETE 1K [pure delete only] | 0.116ms | 33.84ms | 0.435ms | 3.8x faster |
| Window ROW_NUMBER PARTITION BY city | 0.320ms | 517.65ms | 46.18ms | 144x faster |
| FTS Index Build (1M rows) | 849.89ms | 1.55s | 1.09s | 1.3x faster |
| FTS Search ('Electronics') | 0.129ms | 21.49ms | 22.22ms | 167x faster |
| Single-threaded Q/s | 1326.5 Q/s | 6.3 Q/s | 388.7 Q/s | 3.4x faster |
| Concurrent Q/s (4 threads) | 1999.9 Q/s | 22.9 Q/s | 739.1 Q/s | 2.7x faster |
Summary: wins 29/29 benchmarks. "Cold" = fresh DB open per iteration; "warm" = cached backend.
Cold comparison is fair: all three engines measured without gc.collect() interference.
Reproduce: python benchmarks/bench_vs_sqlite_duckdb.py --rows 1000000
Server Protocols
ApexBase ships two complementary server protocols for external access:
| Protocol | Port | Best for | Binary / CLI |
|---|---|---|---|
| PG Wire | 5432 | DBeaver, psql, DataGrip, BI tools | apexbase-server |
| Arrow Flight | 50051 | Python (pyarrow), Go, Java, Spark | apexbase-flight |
Combined Launcher (Both Servers at Once)
# Start PG Wire + Arrow Flight simultaneously
# Custom ports
# Disable one server
| Flag | Default | Description |
|---|---|---|
--dir, -d |
. |
Directory containing .apex database files |
--host |
127.0.0.1 |
Bind host for both servers |
--pg-port |
5432 |
PostgreSQL Wire port |
--flight-port |
50051 |
Arrow Flight gRPC port |
--no-pg |
— | Disable PG Wire server |
--no-flight |
— | Disable Arrow Flight server |
PostgreSQL Wire Protocol Server
ApexBase includes a built-in PostgreSQL wire protocol server, allowing you to connect using DBeaver, psql, DataGrip, pgAdmin, Navicat, and any other tool that supports the PostgreSQL protocol.
Starting the Server
Method 1: Python CLI (after pip install apexbase)
Options:
| Flag | Default | Description |
|---|---|---|
--dir, -d |
. |
Directory containing .apex database files |
--host |
127.0.0.1 |
Host to bind to (use 0.0.0.0 for remote access) |
--port, -p |
5432 |
Port to listen on |
Method 2: Standalone Rust binary (no Python required)
# Build
# Run
Connecting with Database Tools
The server emulates PostgreSQL 15.0, reports a pg_catalog and information_schema compatible metadata layer, and supports SimpleQuery protocol. No username or password is required (authentication is disabled).
DBeaver
- New Database Connection → choose PostgreSQL
- Fill in connection details:
- Host:
127.0.0.1(or the--hostyou specified) - Port:
5432(or the--portyou specified) - Database:
apexbase(any value accepted) - Authentication: select No Authentication or leave username/password empty
- Host:
- Click Test Connection → Finish
- DBeaver will discover tables and columns automatically via
pg_catalog/information_schema
psql
DataGrip / IntelliJ IDEA
- Database tool window → + → Data Source → PostgreSQL
- Set Host, Port, Database as above; leave User and Password empty
- Click Test Connection → OK
pgAdmin
- Add New Server → General tab: give it a name
- Connection tab: set Host and Port; leave Username as
postgres(ignored) and Password empty - Save — tables appear under Databases > apexbase > Schemas > public > Tables
Navicat for PostgreSQL
- Connection → PostgreSQL
- Set Host, Port; leave User and Password blank
- Test Connection → OK
Other Compatible Tools
Any tool or library that speaks the PostgreSQL wire protocol (libpq) can connect, including:
- TablePlus, Beekeeper Studio, Heidisql
- Python:
psycopg2/asyncpg - Node.js:
pg(node-postgres) - Go:
pgx/lib/pq - Rust:
tokio-postgres/sqlx - Java: JDBC PostgreSQL driver
Example with psycopg2:
=
=
Supported SQL over Wire Protocol
The wire protocol server passes SQL directly to the ApexBase query engine. All SQL features listed in Usage Guide are available, including JOINs, CTEs, window functions, transactions, and DDL.
Metadata Compatibility
The server implements a pg_catalog compatibility layer that responds to common catalog queries:
| Catalog / View | Purpose |
|---|---|
pg_catalog.pg_namespace |
Schema listing |
pg_catalog.pg_database |
Database listing |
pg_catalog.pg_class |
Table discovery |
pg_catalog.pg_attribute |
Column metadata |
pg_catalog.pg_type |
Type information |
pg_catalog.pg_settings |
Server settings |
information_schema.tables |
Standard table listing |
information_schema.columns |
Standard column listing |
SET / SHOW statements |
Client configuration probes |
This enables GUI tools to browse tables, inspect columns, and display data types without modification.
Supported Protocol Features
| Feature | Status |
|---|---|
| Simple Query Protocol | ✅ Fully supported |
| Extended Query Protocol (prepared statements) | ✅ Supported — schema cached, binary format for psycopg3 |
Cross-database SQL (db.table) |
✅ Supported — USE dbname / \c dbname to switch context |
pg_catalog / information_schema |
✅ Compatible layer for GUI tools |
| All ApexBase SQL (JOINs, CTEs, window functions, DDL) | ✅ Full pass-through to query engine |
Limitations
- Authentication is not implemented — the server accepts all connections regardless of username/password
- SSL/TLS is not supported — use an SSH tunnel (
ssh -L 5432:127.0.0.1:5432 user@host) for remote access
Arrow Flight gRPC Server
Arrow Flight sends Arrow IPC RecordBatch directly over gRPC (HTTP/2), bypassing per-row text serialization entirely. It is 4–7× faster than PG wire for large result sets (10K+ rows).
| Query | PG Wire | Arrow Flight | Speedup |
|---|---|---|---|
| SELECT 10K rows | 5.1ms | 0.7ms | 7× faster |
| BETWEEN (~33K rows) | 22ms | 5.6ms | 4× faster |
| Single row / point lookup | ~7.5ms | ~7.9ms | equal |
Starting the Flight Server
Python CLI:
Standalone Rust binary:
Python Client
=
# SELECT — returns Arrow Table
=
= # zero-copy to pandas
= # zero-copy to polars
# DML / DDL
# List available actions
When to Use Arrow Flight vs PG Wire
| Scenario | Recommendation |
|---|---|
| DBeaver / Tableau / BI tools | PG Wire (only option) |
| Python + small queries (<100 rows) | Native API (fastest, in-process) |
| Python + large queries (10K+ rows, remote) | Arrow Flight (4–7× faster than PG wire) |
| Go / Java / Spark workers | Arrow Flight (native Arrow support) |
| Local Python (same machine) | Native API (ApexClient.execute()) |
PyO3 Python API
Both servers are also accessible as blocking Python functions (released GIL):
=
=
Rust Native API
ApexBase can be used directly from Rust as a zero-overhead embedded database — no Python, no FFI, no server process required. The full SQL engine, Arrow-native query results, SIMD vector search, FTS, and transactions are all available from the same Rust API.
Cargo Dependency
[]
# Local checkout
= { = "path/to/ApexBase", = false }
# Git
= { = "https://github.com/BirchKwok/ApexBase.git", = false }
default-features = false disables PyO3/numpy and significantly reduces compile time. Add features = ["server"] or features = ["flight"] if you also need the wire protocol servers.
Rust Quick Start
use ;
use Value;
use DurabilityLevel;
use ColumnType;
use HashMap;
Run the full working example:
Key Rust Types
| Type | Import path | Description |
|---|---|---|
ApexDB |
apexbase::embedded::ApexDB |
Database handle — Clone + Send + Sync |
ApexDBBuilder |
apexbase::embedded::ApexDB (via ApexDB::builder) |
Builder with durability / drop options |
Table |
apexbase::embedded::Table |
Table-scoped operations — Clone + Send + Sync |
ResultSet |
apexbase::embedded::ResultSet |
Query result (Arrow RecordBatch or scalar) |
Row |
apexbase::embedded::Row |
HashMap<String, Value> |
Value |
apexbase::data::Value |
Int64 / Float64 / String / Bool / Binary / FixedList / Null |
ColumnType |
apexbase::storage::on_demand::ColumnType |
Schema type for create_table_with_schema |
DataType |
apexbase::data::DataType |
Schema type for add_column / schema() |
DurabilityLevel |
apexbase::storage::DurabilityLevel |
Fast / Safe / Max |
For the full Rust API reference — all methods, transactions, FTS, vector search, concurrency patterns, and performance notes — see docs/RUST_EMBEDDED_API.md.
Architecture
Python (ApexClient)
|
|-- Arrow IPC / columnar dict --------> ResultView (Pandas / Polars / PyArrow)
|
Rust Core (PyO3 bindings)
|
+-- SQL Parser -----> Query Planner -----> Query Executor
| |
| +-- JIT Compiler (Cranelift) |
| +-- Expression Evaluator (70+ functions) |
| +-- Window Function Engine |
| |
+-- Storage Engine |
| +-- V4 Row Group Format (.apex) |
| +-- DeltaStore (cell-level updates) |
| +-- WAL (write-ahead log) |
| +-- Mmap on-demand reads |
| +-- LZ4 / Zstd compression |
| +-- Dictionary encoding |
| |
+-- Index Manager (B-Tree, Hash) |
+-- TxnManager (OCC + MVCC) |
+-- NanoFTS (full-text search) |
+-- PG Wire Protocol Server (pgwire) |
| +-- DBeaver / psql / DataGrip / pgAdmin |
| +-- pg_catalog & information_schema compat |
| |
+-- Arrow Flight gRPC Server (tonic + HTTP/2) |
+-- pyarrow.flight / Go / Java / Spark |
+-- Arrow IPC — zero serialization overhead |
Storage Format
ApexBase uses a custom V4 Row Group format:
- Each table is a single
.apexfile containing a header, row groups, and a footer - Row groups store columns contiguously with per-column compression (LZ4 or Zstd)
- Low-cardinality string columns are dictionary-encoded on disk
- Null bitmaps are stored per column per row group
- A DeltaStore file (
.deltastore) holds cell-level updates that are merged on read and compacted automatically - WAL records provide crash recovery with idempotent replay
Query Execution
- The SQL parser produces an AST that the query planner analyzes for optimization strategy
- Fast paths bypass the full executor for common patterns (COUNT(*), SELECT * LIMIT N, point lookups, single-column GROUP BY)
- Arrow RecordBatch is the internal data representation; results flow to Python via Arrow IPC with zero-copy when possible
- Repeated identical read queries are served from an in-process result cache
API Reference
ApexClient
Constructor
Database Management
| Method | Description |
|---|---|
use_database(database='default') |
Switch to a named database (creates it if needed) |
use(database='default', table=None) |
Switch database and optionally select/create a table |
list_databases() |
List all databases ('default' always included) |
current_database |
Property: current database name |
Table Management
| Method | Description |
|---|---|
create_table(name, schema=None) |
Create a new table, optionally with pre-defined schema |
drop_table(name) |
Drop a table |
use_table(name) |
Switch active table |
list_tables() |
List all tables in the current database |
current_table |
Property: current table name |
Data Storage
| Method | Description |
|---|---|
store(data) |
Store data (dict, list, DataFrame, Arrow Table) |
from_pandas(df, table_name=None) |
Import from pandas DataFrame |
from_polars(df, table_name=None) |
Import from polars DataFrame |
from_pyarrow(table, table_name=None) |
Import from PyArrow Table |
Data Retrieval
| Method | Description |
|---|---|
execute(sql) |
Execute SQL statement(s) |
query(where, limit) |
Query with WHERE expression |
retrieve(id) |
Get record by _id |
retrieve_many(ids) |
Get multiple records by _id |
retrieve_all() |
Get all records |
count_rows(table) |
Count rows in table |
Data Modification
| Method | Description |
|---|---|
replace(id, data) |
Replace a record |
batch_replace({id: data}) |
Batch replace records |
delete(id) or delete([ids]) |
Delete record(s) |
Column Operations
| Method | Description |
|---|---|
add_column(name, type) |
Add a column |
drop_column(name) |
Drop a column |
rename_column(old, new) |
Rename a column |
get_column_dtype(name) |
Get column data type |
list_fields() |
List all fields |
Full-Text Search
| Method | Description |
|---|---|
init_fts(fields, lazy_load, cache_size) |
Initialize FTS |
search_text(query) |
Search documents |
fuzzy_search_text(query) |
Fuzzy search |
search_and_retrieve(query, limit, offset) |
Search and return records |
search_and_retrieve_top(query, n) |
Top N results |
get_fts_stats() |
FTS statistics |
disable_fts() / drop_fts() |
Disable or drop FTS |
Vector Search
| Method | Description |
|---|---|
topk_distance(col, query, k=10, metric='l2', id_col='_id', dist_col='dist') |
Single-query TopK: returns ResultView with id and distance columns |
batch_topk_distance(col, queries, k=10, metric='l2') |
Batch TopK: ndarray of shape (N, k, 2) — ids and distances |
Utility
| Method | Description |
|---|---|
flush() |
Flush data to disk |
set_auto_flush(rows, bytes) |
Set auto-flush thresholds |
get_auto_flush() |
Get auto-flush config |
estimate_memory_bytes() |
Estimate memory usage |
close() |
Close the client |
ResultView
| Method / Property | Description |
|---|---|
to_pandas(zero_copy=True) |
Convert to pandas DataFrame |
to_polars() |
Convert to polars DataFrame |
to_arrow() |
Convert to PyArrow Table |
to_dict() |
Convert to list of dicts |
scalar() |
Get single scalar value |
first() |
Get first row as dict |
get_ids(return_list=False) |
Get record IDs |
shape |
(rows, columns) |
columns |
Column names |
__len__() |
Row count |
__iter__() |
Iterate over rows |
__getitem__(idx) |
Index access |
Documentation
Additional documentation is available in the docs/ directory.
License
Apache-2.0