Use this class to configure the IDriver.
Config
This const defines the value of infinite in terms of configuration properties.
This const defines the value of infinite interval in terms of configuration properties.
A certificate provider that will be used to provide the client certificate when a new connection is established.
The maximum waiting time to either acquire an idle connection from the pool when connection pool is full or create a new connection when pool is not full.
Note that if there is a client certificate provider set, the time taken to fetch the certificate will be included in the connection acquisition timeout, so if fetching the certificate is particularly slow, it might be necessary to increase the timeout.The idle timeout on pooled connections. A connection that has been idled in connection pool for longer than the given timeout is stale and will be closed once it is seen. Use InfiniteInterval to disable idle time checking.
Pooled connections that have been idle in the pool for longer than this timeout will be tested before they are used again, to ensure they are still live. If this option is set too low, an additional network call will be incurred when acquiring a connection, which causes a performance hit.
If this is set high, you may receive sessions that are backed by no longer live connections, which will lead to exceptions in your application. Assuming the database is running, these exceptions will go away if you retry acquiring sessions. Hence, this parameter tunes a balance between the likelihood of your application seeing connection problems, and performance. You normally should not need to tune this parameter. No connection liveness check is done by default. Value 0 means connections will always be tested for validity. Values less than 0 are not allowed.The connection timeout when establishing a connection with a server.
The default read buffer size which the driver allocates for its internal buffers.
The default write buffer size which the driver allocates for its internal buffers.
The use of encryption for all the connections created by the IDriver.
The default fetch size. Since Bolt v4 (Neo4j 4.0+), the query running result (records) are pulled from server in batches. This fetch size defines how many records to pull in each batch. Use Infinite to disable batching and always pull all records in one batch instead.
The connections to support ipv6 addresses.
The ILogger instance to be used to receive all logs produced by this driver.
The maximum connection lifetime on pooled connections. A connection that has been created for longer than the given time will be closed once it is seen. Use InfiniteInterval to disable connection lifetime checking.
The max connection pool size.
The max idle connection pool size. If the value of this is not internal set, then it will default to be the same as MaxConnectionPoolSize
The size when internal read buffers reach, will be released for garbage collection. If reading large records (nodes, relationships or paths) and experiencing too much garbage collection consider increasing this size to a reasonable amount depending on your data.
The maximum transaction retry timeout.
The size when internal write buffers reach, will be released for garbage collection. If writing large values and experiencing too much garbage collection consider increasing this size to a reasonable amount depending on your data.
The configuration for the driver's underlying message reading from the network.
The configuration for setting which notifications the server should send to the client.
This configuration is used for all queries executed by the driver unless otherwise overriden by SessionConfigBuilder for the scope of a single session.
Gets or internal sets a custom server address resolver used by the routing driver to resolve the initial address used to create the driver. Such resolution happens: 1) during the very first rediscovery when driver is created. 2) when all the known routers from the current routing table have failed and driver needs to fallback to the initial address.
The socket keep alive option.
The configuration for whether the driver attempts to send telemetry data.
The telemetry collected covers high level usage of the driver and does not include any queries or parameters.
Current collected metrics:
The negotiator to use when establishing a TLS connection. If this is null, the driver will use the default negotiator.|
The TLS version to use when establishing a connection.
Specifies which TrustManager implementation should be used while establishing trust via TLS.
Used to get and set the User Agent string. If not used the default will be "neo4j-dotnet/x.y" where x is the major version and y is the minor version.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4