Neo4j-OGM 4.x Database

[mike_blum_neo4j]

Given the latest release of neo4j-ogm is now using the updated 4.x driver:

GitHub

neo4j/neo4j-ogm

Java Object-Graph Mapping Library for Neo4j. Contribute to neo4j/neo4j-ogm development by creating an account on GitHub.

I'm having trouble finding the docs for how to configure the default database for the OGM driver to connect to on startup (let's say test.db). Today that's handled at the neo4j.conf level but with multi-tenant databases that now relies on the client.

Looking at the SDN-RX project this is done using the driver directly:

Neo4j Graph Database Platform

Spring Data Neo4j RX - Neo4j Graph Database Platform

Developer Guides Getting Started Getting Started What is a Graph Database? Intro to Graph DBs Video Series Concepts: RDBMS to Graph Concepts: NoSQL to Graph Getting Started Resources Neo4j Graph Platform Graph Platform Overview Neo4j Desktop Intro...

Given the tight coupling of Spring with OGM we're looking to see if we can use 4.x with OGM + multi-tenency before migrating to SDN-RX in the future.

Was thinking the relevant attributes would be found here? https://neo4j.com/developer/java-driver-spring-boot-starter/#_configuration_options

[nielsson4711]

Along the spring default, you configure the default ogm connection within "application.properties" as described in https://neo4j.com/developer/spring-data-neo4j-rx/ , section "2.2.3. Configuration".
Using more elaborated spring configuration options as "profiles", you could end up having a variety of property files like "application-dev.properties", "application-test.properties", "application-integration.properties", each with different database configuration settings.
This is also possible using YAML files.
Studying the spring configuration options, you find a bunch helpful ways to accomplish the most elaborated "default", "profiled", "fallback" configurations.

Looking at the driver configuration for multi tenancy:
You can apply a multi tenancy schema by
a) one database engine instance accessed by one ip socket address serving one database configured with access rights and roles along the tenancy model
b) one database engine instance accessed by one ip socket address serving multiple databases, optionally configured with access rights and roles along the tenancy model. the client is required to explicitly address the database instance wanted aka "USE "
c) multiple database engine instances, each accessed by another ip socket address serving one or multiple databases, optionally configured with access rights and roles along the tenancy model. the . Or you have multiple different database engine instance, each with a different socket address.

You will address a certain database engine instance by a TCP/IP socket connection consisting of hostname/ip and port. ( e.g. fabric configuration: https://neo4j.com/docs/operations-manual/4.0-preview/fabric/configuration/)

[mike_blum_neo4j]

Right - using Neo4jRX there are a litany of options for configuring the database when using the driver directly. My question surrounds configuring the Spring beans / properties to connect to a database on Spring context startup. Its also better articulated here as well:

github.com/neo4j/neo4j-java-driver-spring-boot-starter

Neo4j 4.0 multiple database support?

opened 11:43PM - 16 Dec 19 UTC

SledgeHammer01

Hi, I'm using the latest driver (I think) in Spring: <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-data-neo4j</artifactId> </dependency> <dependency> <groupId>org.neo4j.driver</groupId> <artifactId>neo4j-java-driver-spring-boot-starter</artifactId> <version>4.0.0</version> </dependency> And I'm using...

[nielsson4711]

Hello Mike
I provided with an answer to @SledgeHammer01, I could imagine it will also will support your issue.

Best regards
N

[mike_blum_neo4j · Accepted solution]

Thanks to @michael.simons cc @gerrit.meier this should work nicely for the time-being:

github.com/neo4j/neo4j-ogm

GH-744 - Make database configurable.

committed 10:44AM - 14 Jan 20 UTC

michael-simons

+77 -6

This makes the database configurable in a Bolt transport scenario against a 4.0 database. All queries will be executed in the...