ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #neo4j
Neo4j implements the ISO 8601 standard for temporal data, allowing DateTime objects to store specific timezone identifiers or offsets. This capability is essential for maintaining regional context across distributed datasets. A design challenge arises when converting these zoned representations into LocalDateTime for regional reporting. Because LocalDateTime
Goal: Determine whether an application should implement its own retry logic when the Neo4j Bolt driver returns Neo.ClientError.Security.Unauthorized due to a temporary authentication glitch. Constraint: The driver treats this error as non‑retryable and does not retry the authentication exchange, even if the underlying TCP connection is reconnected. Uncertain
Neo4j Browser presents query results as an interactive graph drawn on an HTML5 canvas. Because canvas pixels do not expose per-node roles, names, or relationship information to the accessibility tree, keyboard-only and screen-reader users cannot traverse a returned graph the way they can traverse ordinary DOM content. The Cypher editor accepts keyboard input
Restore goal I need to restore an online backup taken with neo4j-admin backup into a Neo4j 5.x instance, and the backup was created on an earlier major version. The goal is a point-in-time recovery that preserves node and relationship counts, indexes, and any stored procedures or user-defined functions, without a separate manual data migration step. Constrai
RBAC Privilege Update Propagation Neo4j’s role‑based access control (RBAC) allows administrators to fine‑tune permissions for node labels and relationship types. When a role’s privileges are altered—such as adding or revoking read or write access—there is uncertainty about how quickly those changes take effect for users who are already connected to the datab
The precise goal is to identify the connection pool size threshold at which Neo4j Bolt session queueing latency emerges when client request concurrency exceeds the default capacity. Default pool sizing of 100 connections may not scale uniformly across workloads that interleave short read operations with longer write transactions. Understanding how pool satur
Goal Ensure that Cypher queries reflect the latest schema state without manual intervention. Constraints & Uncertainty Neo4j’s plan cache stores compiled execution plans to avoid re‑planning. The cache is not automatically invalidated when indexes, constraints, or labels are added or removed. Consequently, a query that previously used an index may contin
The goal is to understand why Neo4j exhibits a steady increase in on‑heap memory while the off‑heap page cache size stays constant during sustained write‑heavy transactions. The environment uses the default dbms.memory.pagecache.size setting (≈50 % of RAM) and exposes JMX metrics such as neo4j.memory.heap.used and neo4j.pagecache.memory.used for observation.
Neo4j causal clustering configures the cluster.join_timeout parameter, defaulting to 60 seconds, to manage member discovery during formation. Network partitions that isolate nodes before quorum is reached generate log entries such as 'Cluster formation failed: timeout waiting for initial hosts', indicating unresolved membership. The conditions under which a