You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/neo4j_uc_jdbc_guide.md
+11-9Lines changed: 11 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,8 @@ Upload these JARs to a Unity Catalog Volume:
44
44
45
45
**Note:** The version numbers in this guide reflect the versions available at the time of writing. If you are using a different version, adjust the JAR filenames and references accordingly.
46
46
47
+
**Important:** The `java_dependencies` option in `CREATE CONNECTION TYPE JDBC` only supports Unity Catalog Volume paths (e.g., `/Volumes/catalog/schema/jars/`). Cluster-installed libraries (Maven coordinates, uploaded JARs) cannot be referenced here — they are a separate system. JARs must be uploaded to a UC Volume and referenced by their Volume path.
48
+
47
49
Example path: `/Volumes/catalog/schema/jars/`
48
50
49
51
### 3. Cluster Libraries
@@ -56,7 +58,7 @@ For comprehensive testing, install these libraries on your cluster:
56
58
| neo4j (Python) | 6.0.2 | Neo4j Python Driver |
57
59
| neo4j-jdbc-full-bundle | 6.10.5 | JDBC driver (cluster library for Direct JDBC) |
58
60
59
-
For UC JDBC only, the cluster libraries are optional—the JARs are loaded from the UC Volume.
61
+
For UC JDBC connections, cluster libraries are **not used**. The `java_dependencies` option only accepts UC Volume paths — cluster-installed libraries (Maven coordinates or uploaded JARs) cannot be referenced in `CREATE CONNECTION`. The JDBC JARs must be stored in a UC Volume.
0 commit comments