| Method and Description |
|---|
| org.neo4j.driver.exceptions.Neo4jException.neo4jErrorCode() |
| org.neo4j.driver.Session.reset()
This method should not be used and violates the expected usage pattern of
Session objects.
They are expected to be not thread-safe and should not be shared between thread. However this method is only
useful when Session object is passed to another monitoring thread that calls it when appropriate.
It is not useful when Session is used in a single thread because in this case Session.close()
can be used. Since version 3.1, Neo4j database allows users to specify maximum transaction execution time and
contains procedures to list and terminate running queries. These functions should be used instead of calling
this method. |
| org.neo4j.driver.summary.ServerInfo.version()
in 4.3, please use
ServerInfo.agent(), ServerInfo.protocolVersion(), or call the dbms.components procedure instead.
Method might be removed in the next major release. |
| org.neo4j.driver.Config.ConfigBuilder.withRoutingFailureLimit(int)
in 1.2 because driver memorizes seed URI used during construction and falls back to it at
runtime when all other known router servers failed to respond. Driver is also able to perform DNS lookup
for the seed URI during rediscovery. This means updates of cluster members will be picked up if they are
reflected in a DNS record. This configuration allowed driver to retry rediscovery procedure and postpone
failure. Currently there exists a better way of doing retries via
Session.readTransaction(TransactionWork) and Session.writeTransaction(TransactionWork).
Method will be removed in the next major release. |
| org.neo4j.driver.Config.ConfigBuilder.withRoutingRetryDelay(long, TimeUnit)
in 1.2 because driver memorizes seed URI used during construction and falls back to it at
runtime when all other known router servers failed to respond. Driver is also able to perform DNS lookup
for the seed URI during rediscovery. This means updates of cluster members will be picked up if they are
reflected in a DNS record. This configuration allowed driver to retry rediscovery procedure and postpone
failure. Currently there exists a better way of doing retries via
Session.readTransaction(TransactionWork) and Session.writeTransaction(TransactionWork).
Method will be removed in the next major release. |