kglite-bolt-server-0.10.2 is not a library.
kglite-bolt-server
Bolt v5.x protocol server for kglite
knowledge graphs. A pure-Rust single binary speaking the Neo4j
wire protocol — the Neo4j driver ecosystem (Python / JS / Java /
Go / .NET drivers, Cypher Shell, Neo4j Browser, BloodHound,
LangChain's Neo4jGraph) plugs in unchanged.
Then point any Neo4j-aware client at bolt://localhost:7687 and
run Cypher against the loaded .kgl graph.
Features (Phase F)
- Bolt v5.x handshake + PackStream framing (handshake versions 5.0 / 5.1 / 5.2 / 5.3 / 5.4 advertised).
neo4j://routing URIs via single-server routing table (--advertise-addrfor reverse-proxy deployments).- TLS via
--tls-cert+--tls-key(drivers connect withbolt+s://orneo4j+s://). db.labels()/db.relationshipTypes()yield Neo4j-conventional column names (label,relationshipType).- Optimistic concurrency control on commit — concurrent
writers whose snapshots become stale see
Neo.ClientError.Transaction.ConflictDetected. Retry on the client side. - Zero PyO3 in the binary — no libpython link, no Python
runtime required.
cargo tree -p kglite-bolt-server | grep pyo3returns empty.
CLI
kglite-bolt-server [OPTIONS] --graph <PATH>
Options:
--graph <PATH> .kgl graph file to serve
--bind <ADDR> Bind address [default: 127.0.0.1]
--port <PORT> Port [default: 7687]
--readonly Reject mutations
--auth <USER:PASS> Basic auth credentials
--idle-timeout <SECS> Per-session idle timeout
--max-sessions <N> Max concurrent sessions
--advertise-addr <HOST:PORT> Address advertised in routing table (for neo4j:// URIs)
--tls-cert <PATH> PEM-encoded TLS certificate chain
--tls-key <PATH> PEM-encoded TLS private key
Documentation
- Bolt server operator guide — deployment patterns, driver compatibility, OCC retry shape.
- kglite Rust API — for embedders who want the engine directly without the Bolt frontend.
License
MIT — see LICENSE.