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
* Connect with token to the cloud instance:<br>`jdbc:ydb:grpcs://<host>:2135/path/to/database?tokenFile=~/my_token`
16
+
* Connect with service account to the cloud instance:<br>`jdbc:ydb:grpcs://<host>:2135/path/to/database?saKeyFile=~/sa_key.json`
16
17
3) Execute queries, see example in [YdbDriverExampleTest.java](jdbc/src/test/java/tech/ydb/jdbc/YdbDriverExampleTest.java)
17
18
18
19
### Usage with Maven
@@ -25,21 +26,17 @@ Specify the YDB JDBC driver in the dependencies:
25
26
<dependency>
26
27
<groupId>tech.ydb.jdbc</groupId>
27
28
<artifactId>ydb-jdbc-driver</artifactId>
28
-
<version>2.2.3</version>
29
+
<version>2.3.2</version>
29
30
</dependency>
30
31
31
32
<!-- Shaded version with included dependencies -->
32
33
<dependency>
33
34
<groupId>tech.ydb.jdbc</groupId>
34
35
<artifactId>ydb-jdbc-driver-shaded</artifactId>
35
-
<version>2.2.3</version>
36
+
<version>2.3.2</version>
36
37
</dependency>
37
38
</dependencies>
38
39
```
39
-
### Using QueryService mode
40
-
By default JDBC driver executes all queries via TableService, so it brings corresponding [limitations](https://ydb.tech/docs/en/concepts/limits-ydb#query).
41
-
To eliminate these limitations you can try a new experimentail [QueryService](https://ydb.tech/docs/en/conceptrs/query_service) mode by passing property `useQueryService=true` to the JDBC URL
42
-
43
40
### Authentication modes
44
41
45
42
YDB JDBC Driver supports the following [authentication modes](https://ydb.tech/en/docs/reference/ydb-sdk/auth):
@@ -52,19 +49,18 @@ YDB JDBC Driver supports the following [authentication modes](https://ydb.tech/e
52
49
### Driver properties reference
53
50
54
51
Driver supports the following configuration properties, which can be specified in the URL or passed via extra properties:
55
-
*`saFile` - service account key for authentication, can be passed either as literal JSON value or as a file reference;
52
+
*`saKeyFile` - file location of service account key for authentication;
53
+
*`tokenFile` - file location with token value for token based authentication;
56
54
*`iamEndpoint` - custom IAM endpoint for authentication via service account key;
57
-
*`token` - token value for authentication, can be passed either as literal value or as a file reference;
58
55
*`useMetadata` - boolean value, true if metadata authentication should be used, false otherwise (and default);
59
56
*`metadataURL` - custom metadata endpoint;
60
57
*`localDatacenter` - name of the datacenter local to the application being connected;
61
58
*`secureConnection` - boolean value, true if TLS should be enforced (normally configured via `grpc://` or `grpcs://` scheme in the JDBC URL);
62
59
*`secureConnectionCertificate` - custom CA certificate for TLS connections, can be passed either as literal value or as a file reference.
63
60
64
-
File references for `saFile`, `token` or `secureConnectionCertificate` must be prefixed with the `file:` URL scheme, for example:
0 commit comments