Skip to content

[Java] Value Mapping feature #479

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: dev
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions java-manual/modules/ROOT/content-nav.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
* xref:install.adoc[Installation]
* xref:connect.adoc[Connect to the database]
* xref:query-simple.adoc[Query the database]
* xref:value-mapping.adoc[]

* *Advanced usage*

Expand Down
11 changes: 7 additions & 4 deletions java-manual/modules/ROOT/pages/query-simple.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ Once you have xref:connect.adoc[connected to the database], you can execute <<Cy
For queries with earlier versions, use xref:transactions.adoc[sessions and transactions].


[#write]
== Write to the database

To create two nodes representing persons named `Alice` and `David`, and a relationship `KNOWS` between them, use the Cypher clause link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/create/[`CREATE`]:
Expand Down Expand Up @@ -38,6 +39,7 @@ System.out.printf("Created %d records in %d ms.%n",
<4> The xref:result-summary.adoc[summary of execution] returned by the server


[#read]
== Read from the database

To retrieve information from the database, use the Cypher clause link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/match/[`MATCH`]:
Expand Down Expand Up @@ -71,16 +73,15 @@ System.out.printf("The query %s returned %d records in %d ms.%n",
<1> `records` contains the result as a list of link:https://neo4j.com/docs/api/java-driver/{java-driver-version}/org.neo4j.driver/org/neo4j/driver/Record.html[`Record`] objects
<2> `summary` contains the xref:result-summary.adoc[summary of execution] returned by the server

[TIP]
====
Properties inside a link:https://neo4j.com/docs/api/java-driver/{java-driver-version}/org.neo4j.driver/org/neo4j/driver/Record.html[`Record`] object are embedded within link:https://neo4j.com/docs/api/java-driver/{java-driver-version}/org.neo4j.driver/org/neo4j/driver/Value.html[`Value`] objects.
To extract and cast them to the corresponding Java types, use `.as<type>()` (eg. `.asString()`, `asInt()`, etc).
For example, if the `name` property coming from the database is a string, `record.get("name").asString()` will yield the property value as a `String` object.

For more information, see xref:data-types.adoc[].
====

Another way of extracting values from returned records is by xref:value-mapping.adoc[mapping them to objects].


[#update]
== Update the database

To update a node's information in the database, use the Cypher clauses link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/match/[`MATCH`] and link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/set/[`SET`]:
Expand Down Expand Up @@ -129,7 +130,9 @@ System.out.println(summary.counters().containsUpdates());
<3> Create a new `:KNOWS` relationship outgoing from the node bound to `alice` and attach to it the `Person` node named `Bob`


[#delete]
== Delete from the database

To remove a node and any relationship attached to it, use the Cypher clause link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/delete/[`DETACH DELETE`]:

.Remove the `Alice` node and all its relationships
Expand Down
176 changes: 176 additions & 0 deletions java-manual/modules/ROOT/pages/value-mapping.adoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,176 @@
= Map query results to objects

When xref:query-simple.adoc#read[working with values coming from a query result], you have to manually extract their properties and convert them to the relevant Java types.
For example, to retrieve the `name` property as a string, you have to do `person.get("name").asString()`.

With the driver's Value Mapping feature, you can declare a Java Record containing the specification of the values your query is expected to return, and ask the driver to use that class to spawn new objects from a query result.


== Map driver values to a local class

To map records into objects, define a link:https://docs.oracle.com/en/java/javase/17/language/records.html[Java Record] having the same components as the keys returned by the query.
**The constructor arguments must match exactly the query return keys**, and they are case-sensitive.

The most straightforward option is to use a link:https://docs.oracle.com/en/java/javase/17/language/records.html[Java Record], but using a standard class with a constructor that matches the query result keys works as well.
Either way, you provide the class definition to the driver through the link:https://neo4j.com/docs/api/java-driver/current/org.neo4j.driver/org/neo4j/driver/Value.html#as(java.lang.Class)[`Value.as()`] method.

.Map `:Person` nodes onto a `Person` record objects
[source, java]
----
package demo;

import org.neo4j.driver.AuthTokens;
import org.neo4j.driver.Driver;
import org.neo4j.driver.GraphDatabase;
import org.neo4j.driver.QueryConfig;

public class App {

private static final String dbUri = "<database-uri>";
private static final String dbUser = "<username>";
private static final String dbPassword = "<password>";

public static void main(String... args) {
try (var driver = GraphDatabase.driver(URI, AuthTokens.basic(USER, PASSWORD))) {
record Person(String name, Integer age) {}
var persons = driver.executableQuery("MERGE (p:Person {name: 'Margarida', age: 29}) RETURN p")
.withConfig(QueryConfig.builder().withDatabase("neo4j").build())
.execute()
.records()
.stream()
.map(record -> record.get("p").as(Person.class))
.toList();
System.out.println(persons.get(0)); // Person[name=Margarida, age=29]
}
}
}
----

Arguments that don't have a matching property receive a `null` value.
If the argument does not accept a `null` value (for ex. primitive types), an xref:constructors[alternative constructor] that excludes it must be available.
The example above uses the type `Integer` over the primitive `int` to account for nodes missing the `age` property.

Declaring the `record` object side-by-side with the query that uses it is a convenient way to obtain results on which it is easy to extract properties.
However, because the class is defined in a local scope, its type cannot be referenced outside of the method where it is defined.
As a result, such type may not be used as a return type of the method: you need to process the mapped value in the same function or ensure it implements a type that is accessible outside of the given method.
Another solution is to declare the `record` object as a `public` member of the class, or to create a new standalone class containing your `record` definition.
This will make the mapped object available out of the scope of the method in which it was defined.

[NOTE]
====
While constructor arguments with specific complex types (ex. `record Friends(List<String> names) {}`) are supported, constructor arguments with generic complex types (ex. `record Friends<T>(List<T> names) {}`) are not supported.
====


== Map properties with different names (`@Property`)

A record's property names and its query return keys can be different.
For example, consider a node `(:Person {name: "Alice"})`.
The returned keys for the query `MERGE (p:Person {name: "Alice"}) RETURN p.name` are `p.name`, even if the property name is `name`.
Similarly, for the query `MERGE (pers:Person {name: "Alice"}) RETURN pers.name`, the return keys are `pers.name`.

You can always alter the return key with the Cypher operator link:https://neo4j.com/docs/cypher-manual/current/clauses/return/#return-column-alias[`AS`] (ex. `MERGE (p:Person {name: "Alice"}) RETURN p.name AS name`), or use the `@Property(<dbPropertyName>)` annotation to specify the property name that the following constructor argument should map to.

.Map properties `name`/`age` to the object attributes `firstName`/`Years`
[source, java]
----
// import org.neo4j.driver.mapping.Property;

record Person(@Property("name") String firstName, @Property("age") Integer Years) {}
var persons = driver.executableQuery("MERGE (p:Person {name: 'Margarida', age: 29}) RETURN p")
.withConfig(QueryConfig.builder().withDatabase("neo4j").build())
.execute()
.records()
.stream()
.map(record -> record.get("p").as(Person.class))
.toList();
System.out.println(persons.get(0)); // Person[firstName=Margarida, Years=29]
----


== Map driver records to a local class

The earlier examples have mapped a driver `Value` (for example a node identified with `p`) to a class.
You can also use the mapping feature with driver `Record` instances, through the link:https://neo4j.com/docs/api/java-driver/current/org.neo4j.driver/org/neo4j/driver/Record.html#as(java.lang.Class)[`Record.as()`] method.

.Return keys `name`/`p.age` are mapped to the object attributes `Name`/`Age`
[source, java]
----
// import org.neo4j.driver.mapping.Property;

record Person(String name, @Property("p.age") Integer age) {}
var persons = driver.executableQuery("""
MERGE (p:Person {name: 'Margarida', age: 29})
RETURN p.name AS name, p.age
""")
.withConfig(QueryConfig.builder().withDatabase("neo4j").build())
.execute()
.records()
.stream()
.map(record -> record.as(Person.class))
.toList();
System.out.println(persons.get(0)); // Person[name=Margarida, age=29]
----


[#constructors]
== Work with multiple constructors

Your Java record class can contain multiple constructors.
In that case, the driver picks one basing on the following criteria (in order of priority):

- Most matching properties
- Least mis-matching properties

At least one property must match for a constructor to work with the mapping.

.An additional constructor to handle the optional `age` property
[source, java]
----
// import org.neo4j.driver.mapping.Property;

record Person(String name, int age) {
public Person(@Property("name") String name) {
this(name, -1);
}
}
var persons = driver.executableQuery("MERGE (p:Person {name: 'Axel'}) RETURN p")
.withConfig(QueryConfig.builder().withDatabase("neo4j").build())
.execute()
.records()
.stream()
.map(record -> record.get("p").as(Person.class))
.toList();
----

[NOTE]
====
The compiler renames constructor parameters by default, unless the compiler `-parameters` option is used or the parameters belong to the cannonical constructor of `java.lang.Record`.

In the example above, the constructor containing only `name` uses the `@Property` annotation even if it doesn't specify a different name than the constructor argument. This is needed because that is not the canonical constructor.
====


[#insert-update]
== Insert and update data

You can also use the mapping feature to insert or update data, by creating an instance of the Java Record object that serves as a blueprint for your object and then passing it to the query as a parameter.

.Create and update a `:Person` node
[source, java]
----
record Person(String name, int age) {}

var person = new Person("Lucia", 29);
driver.executableQuery("CREATE (:Person $person)")
.withParameters(Map.of("person", person))
.execute();

var happyBirthday = new Person("Lucia", 30);
driver.executableQuery("""
MATCH (p:Person {name: $person.name})
SET person += $person
""")
.withParameters(Map.of("person", happyBirthday))
.execute();
----