Establish Bolt protocol version negotiation handshake
Clients and servers must negotiate the highest mutually supported Bolt protocol version during connection establishment to ensure backward compatibility across releases.
Decisions are extracted from the evidence, then kept honest: a later revision or reversal is recorded rather than silently overwriting the original.
Decisions are extracted from the evidence, then kept honest: a later revision or reversal is recorded rather than silently overwriting the original.
Loading records…
Origin·15 Mar 2018
Clients and servers must negotiate the highest mutually supported Bolt protocol version during connection establishment to ensure backward compatibility across releases.
Revision·20 Nov 2020
Each Bolt protocol version must have a documented deprecation schedule (minimum 2 major releases) before removal to give driver maintainers migration time.
Revision·12 Jun 2023
Bolt 5.x introduces compact binary encoding for property values and optional telemetry metadata in response headers, requiring updated negotiation logic.
Origin·22 Jan 2019
Transaction lifecycle (OPEN → EXECUTING → COMMITTING → COMMITTED/ROLLED_BACK) must be enforced via compare-and-swap state transitions to prevent race conditions in concurrent access.
Revision·18 Apr 2021
Read-only transactions that don't require explicit locks can bypass the lock manager entirely, reducing contention for analytical workloads.
Reversal·3 Sept 2021
Optimistic locking for concurrent schema changes (index/constraint creation) caused livelock under high contention; reverted to pessimistic schema lock with queue.
Origin·30 Aug 2018
Replace rule-based planner with cost-based optimizer using statistical cardinality estimates for join ordering and index selection.
Revision·14 Feb 2020
Cache compiled query plans keyed by normalized query text and parameter types; invalidate on schema changes affecting referenced labels/relationship types/properties.
Revision·8 Nov 2022
Enable runtime statistics collection during query execution; if actual cardinalities deviate >10x from estimates, trigger re-optimization of remaining operators.