Data sources

This is the public preview documentation of Neo4j Virtual Graph. To provide feedback, please use the feedback form you were granted access to.

During the public preview, we advise you not to use sensitive or production data with Virtual Graph.

The file datasource.json determines which JDBC driver is loaded and ultimately also which secrets are supported. The data source definition requires a type field and all data sources support a nested object additionalProperties:

{
  "type": "databricks",
  "additionalProperties": {
    "loglevel": "6",
    "logpath": "/foo/bar"
  }
}

Anything in additionalProperties except for hikari.minimumIdle, hikari.maximumPoolSize and jdbc.fetch_size are passed as they are to the underlying datasource definition defined by the vendor’s JDBC driver.

The value of type determines which JDBC driver is loaded. The following values are valid:

  • bigquery

  • databricks

  • duckdb

  • generic

  • snowflake

  • sqlite

All specific properties for a type are discussed in the corresponding JDBC driver sections. The properties, such as catalog and schema or the remote warehouse, are vendor-specific. The generic type is an escape hatch for arbitrary JDBC drivers that Virtual Graph does not treat as first-class citizens. See Generic.