Native
Connecting via API
The following shows the means of connecting to Kinetica via the various APIs available.
HTTP Connections
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HTTPS Connections with Certificate Validation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HTTPS Connections without Certificate Validation
Note
Using these setups, no certificate validation of any kind will be performed; not recommended for production deployments.
To bypass certificate checks in JDBC, see Secure Connections. To bypass certificate checks in KiSQL, see Parameterized Options.
|
|
|
|
|
|
HTTPS Connections with OIDC/OAuth Authentication
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Compatibility Matrix
The following chart shows the version compatibilities between the various APIs and a target database server. While only the major & minor version numbers (6.2, 7.0, 7.1, 7.2) must match to achieve interoperability, the complete feature set for a given database version can only be utilized via the corresponding API version, depicted below.
Database | C++ | C# | Java | Javascript | Node.js | Python |
---|---|---|---|---|---|---|
6.2 | 6.2.* | 6.2.* | 6.2.* | 6.2.* | 6.2.* | 6.2.* |
7.0.X | 7.0.X | 7.0.X | 7.0.X | 7.0.X | 7.0.X | 7.0.X |
7.1.X | 7.1.X | 7.1.X | 7.1.X | 7.1.X | 7.1.X | 7.1.X |
7.2.X | 7.2.X | 7.2.X | 7.2.X | 7.2.X | 7.2.X | 7.2.X |
Dynamic Schemas
When working with APIs, it is helpful to have an understanding of how data is returned by the database. For a detailed breakdown in Java & Python, see Dynamic Schemas.