The connection properties are the various options that can be used to establish a connection. This section provides a complete list of the options you can configure in the connection settings for this provider. Click the links for further details.For more information on establishing a connection, see Getting Started.
|The Neo4j user account used to authenticate.
|The password used to authenticate the user.
|The server hosting the Neo4j instance. You may optionally prepend a protocol prefix to the server address or name you specify, like https://127.0.0.1 .
|The port on which the Neo4j service is running.
|The default database queried for your Neo4j instance.
|The certificate to be accepted from the server when connecting using TLS/SSL.
|The protocol used by a proxy-based firewall.
|The name or IP address of a proxy-based firewall.
|The TCP port for a proxy-based firewall.
|The user name to use to authenticate with a proxy-based firewall.
|A password used to authenticate to a proxy-based firewall.
|This indicates whether to use the system proxy settings or not. This takes precedence over other proxy settings, so you'll need to set ProxyAutoDetect to FALSE in order use custom proxy settings.
|The hostname or IP address of a proxy to route HTTP traffic through.
|The TCP port the ProxyServer proxy is running on.
|The authentication type to use to authenticate to the ProxyServer proxy.
|A user name to be used to authenticate to the ProxyServer proxy.
|A password to be used to authenticate to the ProxyServer proxy.
|The SSL type to use when connecting to the ProxyServer proxy.
|A semicolon separated list of destination hostnames or IPs that are exempt from connecting through the ProxyServer .
|A filepath which designates the name and location of the log file.
|The verbosity level that determines the amount of detail included in the log file.
|Core modules to be included in the log file.
|A string specifying the maximum size in bytes for a log file (for example, 10 MB).
|A string specifying the maximum file count of log files.
|A path to the directory that contains the schema files defining tables, views, and stored procedures.
|This property restricts the schemas reported to a subset of the available schemas. For example, BrowsableSchemas=SchemaA,SchemaB,SchemaC.
|This property restricts the tables reported to a subset of the available tables. For example, Tables=TableA,TableB,TableC.
|Restricts the views reported to a subset of the available tables. For example, Views=ViewA,ViewB,ViewC.
|Automatically caches the results of SELECT queries into a cache database specified by either CacheLocation or both of CacheConnection and CacheProvider .
|The name of the provider to be used to cache data.
|The connection string for the cache database. This property is always used in conjunction with CacheProvider . Setting both properties will override the value set for CacheLocation for caching data.
|Specifies the path to the cache when caching to a file.
|The tolerance for stale data in the cache specified in seconds when using AutoCache .
|Use offline mode to get the data from the cache instead of the live source.
|This property determines whether or not to cache the table metadata to a file store.
|Limits the number of rows when using the DirectQuery mode. This helps avoid performance issues at design time.
|Whether to detect the foreign keys in ODBC.
|The maximum column size.
|Limits the number of rows returned when no aggregation or GROUP BY is used in the query. This takes precedence over LIMIT clauses.
|A Cypher node label matching expression. The provider exposes all node labels from the matched nodes as views.
|These hidden properties are used only in specific use cases.
|The maximum number of results to return per page from Neo4j.
|This property indicates whether or not to include pseudo columns as columns to the table.
|The type(s) of labels that must be present on the destination nodes of single-hop relationships that the provider will expose as views.
|The node labels that must be present on the source nodes of single-hop relationships, which the provider will expose as views.
|The relationship type(s) of single-hop relationships that the driver will expose as views.
|The maximum number of rows to scan to look for the columns available in a table.
|The runtime key used for licensing.
|The value in seconds until the timeout error is thrown, canceling the operation.
|A filepath pointing to the JSON configuration file containing your custom views.