Repository navigation
Release v22.168.0
Arc applications can now read graphs from Neo4j with the same convenience as MongoDB: a tenant-aware session that opens the right database for the current tenant, concept-aware parameters and results, and connection resolution.
Added
Cratis.Arc.Neo4j:WithNeo4j(...)/AddCratisNeo4j(...)withNeo4jOptions(server, credentials or a password secret key, database prefix,PerNamespaceorSingledatabase mode), one pooled driver per server and identity, and a scopedIGraphSession(read access by default,IGraphSessionFactory.Open(AccessMode)for writes) injectable into queries and services (#3692)- Graph databases are named per event store and namespace with the same algorithm Chronicle's Neo4j graph sink uses, so Arc reads exactly what Chronicle projects; replace
IGraphDatabaseNameResolverorIGraphNamespaceResolverto customize it - Concept values bind as their primitive in Cypher parameters, and query results map back to records with concept-typed properties
- Connection resolution supports Neo4j: resolvers can answer the Bolt URI, the database and the identity, and expired or rejected credentials are resolved again;
Neo4jis a storage value in the connection resolution contract Cratis.Arc.Neo4j.Testingwith a substitutable graph session for specifications- Documentation: Neo4j and a sample under
Samples/Neo4j