ArcadeDB Documentation

The Bolt Conformance Suite is a testing implementation designed to certify the official neo4j Python driver against ArcadeDB's Bolt protocol implementation. It aims to implement all 39 scenarios defined in the bolt/conformance/spec.yaml specification as pytest tests.

Key Technical Details:

• Target File: e2e-python/tests/test_bolt.py
• Test Framework: pytest
• Driver: neo4j (official Python driver) >=6.2.0
• Infrastructure: testcontainers for managing database instances.
• Protocol Support: Tests include both TLS-disabled and TLS-mode scenarios.
• Python Requirements: Python >=3.10 (Python 3.13 used in CI).

ArcadeDB is a multi-model DBMS supporting several data models and query languages:

Supported Models

• Graph Database: Compatible with Neo4j Cypher, Apache Tinkerpop Gremlin, and OrientDB SQL.
• Document Database: Compatible with MongoDB driver, MongoDB queries, and OrientDB SQL.
• Key/Value: Compatible with the Redis driver.
• Search Engine
• Time Series: Supports InfluxDB Line Protocol, Prometheus (remote_write/read), and PromQL.
• Vector Embedding
• Geospatial

Supported Query Languages

• SQL (from OrientDB SQL)
• Cypher (Open Cypher)
• Apache Gremlin (Apache Tinkerpop v3.7.x)
• GraphQL Language
• MongoDB Query Language

The Bolt (Java) Conformance Certification plan aims to expand the Java Bolt certification from 4 smoke tests to the full 39-scenario A1 conformance specification. This is achieved by driving tests using the real neo4j-java-driver to ensure ArcadeDB's Java compatibility matrix is comparable to the JS and Go implementations.

Architecture

The certification uses two layers:

1. e2e layer: Expands RemoteBoltDatabaseIT (using JUnit 5 and @Nested structures) against the arcadedata/arcadedb:latest Testcontainer.
2. bolt-module layer: Adds or extends narrow Integration Tests (ITs) for scenarios that the shared container cannot express, such as specific TLS modes or wire-level type serialization.

A helper assertExpectedFailure is used to reproduce documented gaps (e.g., issue #4890) without causing build failures, similar to the JS it.failing pattern.

The e2e-js directory contains the following test suites:

• src/js-bolt-conformance.test.js: Implements Bolt conformance scenarios against the official neo4j-driver. It covers 39 scenarios including connection, auth, transactions, and data types.
• src/js-bolt-e2e.test.js: Focuses on Bolt variable-length-path regression.
• src/js-pg-e2e.test.js: A smoke test for the PostgreSQL wire protocol.

Note on Driver Versions: This suite currently pins neo4j-driver version ^6.0.1.

The e2e-js Bolt conformance suite is a Jest-based testing framework designed to certify the neo4j-driver (npm) against the ArcadeDB Bolt protocol. It implements 39 scenarios defined in the shared bolt/conformance/spec.yaml.

Key characteristics:

• Official Driver Only: Uses the standard neo4j-driver (^6.0.1) without mocks.
• Traceability: Every test is prefixed with its spec ID (e.g., [TYPE-011]) for easy coverage auditing.
• Gap Documentation: Known protocol gaps are documented using Jest's it.failing() (the equivalent of xfail(strict=True)), which ensures the test fails as expected and alerts developers if the gap is ever fixed.
• Polyglot Parity: The suite mirrors the fixture and seeding strategies used in the Python, Go, and C# conformance suites to ensure comparable results across languages.

This implementation plan outlines the process for propagating destructive and administrative commands—such as drop database, restore database, import database, create user, and drop user—from a Raft leader to all replicas.

Core Architecture:

• New Log Entry Types: DROP_DATABASE_ENTRY and SECURITY_USERS_ENTRY are introduced to the Raft log.
• Extended Entry: INSTALL_DATABASE_ENTRY is extended to include a forceSnapshot flag.
• Raft-First Semantics: Destructive mutations are only applied by the ArcadeStateMachine once the entry has been committed via RaftGroupCommitter.submitAndWait.
• User Replication: Users (stored in server-users.jsonl) are replicated using a HAServerPlugin.replicateSecurityUsers(String) hook, which carries the full JSON content through the log. New peers are seeded with current users via PostAddPeerHandler.

The arcadedb-embedded package provides several key capabilities for Python developers:

• Embedded Mode: Direct database access within the Python process (no network required). For client-server deployments, use the official ArcadeDB server.
• Multi-model Support: Graph, Document, Key/Value, Vector, and Time Series.
• Multiple Query Languages: SQL, OpenCypher, and MongoDB.
• Vector Storage: Store and query vector embeddings with HNSW (JVector) indexing.
• ACID Transactions: Full transaction support via context managers.
• No Java Required: Includes a bundled JRE (~63MB uncompressed).
• High Performance: Direct JVM integration via JPype.

The implementation plan for the e2e-js Bolt conformance suite ensures that every scenario defined in spec.yaml is mapped to a specific task. The suite covers the following functional areas:

• Connection: (T1/T10)
• Auth: (T2)
• Transactions: (T3)
• Causal + Multi-DB: (T4)
• Result Handling: (T5)
• Type Roundtrip: (T6/T7)
• Errors: (T8)
• Protocol: (T9)
• README + Coverage Proof: (T11)

Implementation details include using it.failing for known gaps, it.skip for intentional skips, and specific strategies for fixture management, image resolution, and HTTP-only seeding while maintaining an untouched-regression constraint.