Connecting to Your Cluster

You can connect to your cluster by using the following clients:

Java Thin Client
.NET Thin Client
C++ Thin Client
Python Thin Client
Node.js Thin Client
JDBC
ODBC
Java Thick Client
REST API

Connection URI

All examples below contain the {connectionUri} value. You can get it from the template at the end of provisioning wizard, or

Java Thin Client

Java thin client is a lightweight client that connects to the cluster via a standard socket connection. It does not become a part of the cluster topology, never holds any data, and is not used as a destination for compute calculations. The thin client simply establishes a socket connection to a standard node and performs all operations through that node.

Add the following dependencies to your Maven project:

<repositories>
    <repository>
        <id>GridGain External Repository</id>
        <url>https://www.gridgainsystems.com/nexus/content/repositories/external</url>
    </repository>
</repositories>

<dependencies>
    <dependency>
        <groupId>org.gridgain</groupId>
        <artifactId>ignite-core</artifactId>
        <version>8.8.10</version>
    </dependency>
</dependencies>

Create a client configuration. Replace the USER_NAME placeholder with your cluster URL. Replace the USER_NAME and PASSWORD placeholders with your cluster credentials.

ClientConfiguration cfg = new ClientConfiguration()
        .setAddresses("CONNECTION_URL")
        .setUserName("USER_NAME")
        .setUserPassword("PASSWORD")
        .setSslMode(SslMode.REQUIRED);

Connect to the cluster.

try (IgniteClient client = Ignition.startClient(cfg)) {
    // Use the API.
    ClientCache<Integer, String> cache =  client.getOrCreateCache(new ClientCacheConfiguration()
            .setName("Test")
            .setBackups(1)
    );
    cache.put(1, "foo");
    System.out.println(">>>    " + cache.get(1));
}

For more information on thin clients, please see this article.

.NET Thin Client

Prerequisites:

Supported runtimes: .NET 4.0+, .NET Core 2.0+

Supported OS: Windows, Linux, macOS (any OS supported by .NET Core 2.0+)

Install the GridGain package:

dotnet add package GridGain --version 8.8.10

Create client configuration: Replace the ${HIDDEN_LOGIN} and ${HIDDEN_PASSWORD} with your cluster credentials.

var cfg = new IgniteClientConfiguration
{
    Endpoints = new[] { "${connectionInfo?.urls[0]}:10800" },
    UserName = "${HIDDEN_LOGIN}",
    Password = "${HIDDEN_PASSWORD}",
    SslStreamFactory = new SslStreamFactory()
};

Connect to the cluster.

using (var client = Ignition.StartClient(cfg))
{
    // Use the API.
    var cache = client.GetOrCreateCache<int, string>(new CacheClientConfiguration("test") { Backups = 1 });
    cache.Put(1, "foo");
    Console.Out.WriteLine(">>>    " + cache.Get(1));
}

For more information on .NET Thin Client, please see this article.

Python Thin Client

Please note the following client prerequisites: Python 3.4 or above.

Setting Up

You can install the Python thin client either using pip or from a zip archive.

Using PIP

The python thin client package is called pygridgain. You can install it using the following command:

pip3 install pygridgain

pip install pygridgain

Using ZIP Archive

The thin client can be installed from the zip archive available for download from the GridGain website:

Go to the website and download the GridGain Python Thin Client archive.
Unpack the archive and navigate to the root folder.
Install the client using the command below.

pip3 install .

pip install .

This will install pygridgain in your environment in the so-called "develop" or "editable" mode. Learn more about the mode from the official documentation.

After that, import the GridGain Python thin client:

from pygridgain import Client

Connecting to the Cluster

Create client configuration: Replace the {login} and {password} with your cluster credentials.
```
client = Client(username='{login}', password='{password}', use_ssl=True)
```

Connect to the cluster.

client.connect('${connectionInfo.urls?.[0]}', 10800)

Use the API.

my_cache = client.get_or_create_cache('test')
my_cache.put(1, 'foo')
result = my_cache.get(1)
print(result)

For more information on Python Thin Client, please see this article.

C++ Thin Client

GridGain on-premise comes with a C++ thin client that you can use to work with Nebula clusters.

Setting Up

The source code of the C++ thin clien is available with the GridGain distribution package in the {GRIDGAIN_HOME}/platforms/cpp directory. To start working with it, install the client on your system:

mkdir cmake-build-release

cd cmake-build-release

cmake -DCMAKE_BUILD_TYPE=Release -DWITH_THIN_CLIENT=ON -DWITH_CORE=OFF -DWITH_ODBC=OFF ..

# The following installs Ignite on your system.
make install

Creating a Client Instance

#include <ignite/thin/ignite_client.h>

using namespace ignite::thin;

void main()
{
    // Create a client configuration.
    // Replace {login} and {password} values with cluster credentials.
    IgniteClientConfiguration cfg;
    cfg.SetEndPoints("8adc6033-103a-4088-bed9-8ed1c3e8fa59.gridgain-nebula-test.com:10800");
    cfg.SetUser("{login}");
    cfg.SetPassword("{password}");
    cfg.SetSslMode(SslMode::REQUIRE);

    try
    {
        // Connect to the cluster.
        IgniteClient client = IgniteClient::Start(cfg);

        // Create the cache and put data into it.
        cache::CacheClient<int32_t, std::string> cache = client.GetOrCreateCache<int32_t, std::string>("test");
        cache.Put(1, "foo");
        std::cout << ">>>    " << cache.Get(1) << std::endl;
    }
    catch (const ignite::IgniteError& err)
    {
        std::cerr << err.GetText() << std::endl;
    }
}

For additional information on using C++ thin client, read the extended article in GridGain documentation.

Node.js Thin Client

Prerequisites: Node.js version 8 or higher.

Install the GridGain package: npm install -g @gridgain/thin-client:

const IgniteClient = require('@gridgain/thin-client');
const IgniteClientConfiguration = IgniteClient.IgniteClientConfiguration;
const ObjectType = IgniteClient.ObjectType;
async function performCacheKeyValueOperations() {

Create client configuration: Replace the ${HIDDEN_LOGIN} and ${HIDDEN_PASSWORD} with your cluster credentials.

const igniteClientConfiguration = new IgniteClientConfiguration('${connectionInfo?.urls[0]}:10800').
    setUserName('${HIDDEN_LOGIN}').
    setPassword('${HIDDEN_PASSWORD}').
    setConnectionOptions(true);
  // Connect to the cluster.
  const igniteClient = new IgniteClient();
  try {
    await igniteClient.connect(igniteClientConfiguration);
    // Use the API.
    const cache = (await igniteClient.getOrCreateCache('test')).
              setKeyType(ObjectType.PRIMITIVE_TYPE.INTEGER);
    await cache.put(1, 'foo');
    const value = await cache.get(1);
    console.log(value);
  }
  catch (err) {
    console.log(err.message);
  }
  finally {
    igniteClient.disconnect();
  }
}

For more information on Node.js Thin Client, please see this article.

JDBC

GridGain is shipped with JDBC drivers that allow processing of distributed data using standard SQL statements like SELECT, INSERT, UPDATE or DELETE directly from the JDBC side.

Open a JDBC connection: Replace the ${HIDDEN_LOGIN} and ${HIDDEN_PASSWORD} with your cluster credentials.

try (Connection connection = DriverManager
    .getConnection("jdbc:ignite:thin://${connectionInfo?.urls[0]}:10800" +
    "?user=${HIDDEN_LOGIN}&password=${HIDDEN_PASSWORD}&sslMode=require")) {

Use the API:

try (Statement stmt = connection.createStatement()) {
    stmt.executeUpdate("CREATE TABLE IF NOT EXISTS person (id LONG PRIMARY KEY, name VARCHAR) WITH \"backups=1\"");
    stmt.execute("INSERT INTO person (id, name) VALUES (1, 'John Doe')");
    stmt.execute("INSERT INTO person (id, name) VALUES (2, 'Jane Doe')")

    try (ResultSet rs = stmt.executeQuery("SELECT id, name FROM person")) {
        while (rs.next())
            System.out.println(">>>    " + rs.getString(1) + ", " + rs.getString(2));
    }
}

For more information on JDBC driver, please see this article.

ODBC

GridGain includes an ODBC driver that allows you both to select and to modify data stored in a distributed cache using standard SQL queries and native ODBC API.

Installation

GridGain comes with an ODBC driver. If you use Windows, you can install it immediately. On Linux you will need to build it first. You can find installation and build instructions in GridGain documentation.

Connecting to Cluster

To connect to cluster, use the connection template provided in the GridGain Nebula. Below we will walk through the template step by step:

Make sure to include the required dependencies in your code:

#include <sql.h>
#include <sqlext.h>

#include <stdio.h>
#include <string.h>

We will be using the following code to handle possible issues:


void PrintOdbcErrorStack(SQLSMALLINT handleType, SQLHANDLE handle)
{
    SQLCHAR sqlState[7] = "";

    SQLCHAR message[1024];
    SQLSMALLINT messageLen = 0;

    SQLSMALLINT idx = 1;
    while (true)
    {
        memset(message, 0, sizeof(message));
        memset(sqlState, 0, sizeof(sqlState));

        SQLRETURN ret = SQLGetDiagRec(handleType, handle, idx, sqlState, NULL, message, sizeof(message), &messageLen);

        if (!SQL_SUCCEEDED(ret))
            break;

        printf("[ERROR] %s: %s\n", sqlState, message);
        ++idx;
    }
}

Allocate environment and connection handles:

// Allocates an environment handle.
SQLHENV env;
SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &env);
if (env == NULL)
{
    printf("Can not allocate environment handle\n");
    return;
}

// Allocates a connection handle.
SQLHDBC conn;
SQLAllocHandle(SQL_HANDLE_DBC, env, &conn);
if (conn == NULL)
{
    printf("Can not allocate connection handle\n");
    PrintOdbcErrorStack(SQL_HANDLE_ENV, env);
    return;
}

Specify that ODBC 3 will be used to connect to the cluster:

// Enables support for ODBC 3.
SQLSetEnvAttr(env, SQL_ATTR_ODBC_VERSION, (void*)(SQL_OV_ODBC3), 0);

Connect to the server:

// Creates a connection string.
SQLCHAR connectStr[] =
    "DRIVER={Apache Ignite};"
    "ADDRESS=8adc6033-103a-4088-bed9-8ed1c3e8fa59.gridgain-nebula-test.com:10800;"
    "SSL_MODE=REQUIRE;"
    "SCHEMA=PUBLIC;"
    "USER={login};"
    "PASSWORD={password}";

// Connects to ODBC server.
SQLRETURN ret = SQLDriverConnect(conn, NULL, connectStr, SQL_NTS, NULL, 0, NULL, SQL_DRIVER_COMPLETE);
if (!SQL_SUCCEEDED(ret))
{
    PrintOdbcErrorStack(SQL_HANDLE_DBC, conn);
    return;
}

Allocate a statement handle:

// Allocates a statement handle.
SQLHSTMT statement;
SQLAllocHandle(SQL_HANDLE_STMT, conn, &statement);
if (statement == NULL)
{
    printf("Can not allocate statement handle\n");
    PrintOdbcErrorStack(SQL_HANDLE_DBC, conn);
    return;
}

Create a table in the cluster:

// Creates a table.
SQLCHAR createTableReq[] =
    "CREATE TABLE IF NOT EXISTS TEST "
    "(ID INTEGER PRIMARY KEY, VALUE VARCHAR) "
    "WITH "template=partitioned, cache_name=Test";";

ret = SQLExecDirect(statement, createTableReq, SQL_NTS);
if (!SQL_SUCCEEDED(ret))
{
    PrintOdbcErrorStack(SQL_HANDLE_STMT, statement);
    return;
}

You can find more information on working with ODBC driver in GridGain Documentation.

Java Thick Client

Java thick client (client node) joins the cluster via an internal protocol, receives all of the cluster-wide updates such as topology changes, is aware of data distribution, and can direct a query/operation to a server node that owns a required data set. Plus, Java thick client supports all of the GridGain APIs.

Add the following dependencies to your Maven project:

<repositories>
    <repository>
        <id>GridGain External Repository</id>
        <url>https://www.gridgainsystems.com/nexus/content/repositories/external</url>
    </repository>
</repositories>

<dependencies>
    <dependency>
        <groupId>org.gridgain</groupId>
        <artifactId>gridgain-core</artifactId>
        <version>8.8.10</version>
    </dependency>
    <dependency>
        <groupId>org.gridgain</groupId>
        <artifactId>ignite-indexing</artifactId>
            <version>8.8.10</version>
        </dependency>
</dependencies>

Create client configuration: Replace the {login} and {password} with your cluster credentials.

System.setProperty("IGNITE_EVENT_DRIVEN_SERVICE_PROCESSOR_ENABLED", "true");
SecurityCredentials clientCredentials = new SecurityCredentials("{login}", "{password}");
IgniteConfiguration cfg = new IgniteConfiguration()
        .setClientMode(true)
        .setDiscoverySpi(new TcpDiscoverySpi()
                .setIpFinder(new TcpDiscoveryVmIpFinder()
                        .setAddresses(Collections.singleton(
                                "${connectionInfo?.urls[0]}:47500"))))
        .setCommunicationSpi(new TcpCommunicationSpi()
                .setForceClientToServerConnections(true))
        .setPluginConfigurations(new GridGainConfiguration()
                .setSecurityCredentialsProvider(new SecurityCredentialsBasicProvider(clientCredentials))
                .setRollingUpdatesEnabled(true))
        .setSslContextFactory(new SslContextFactory());

Connect to the cluster.

try (Ignite client = Ignition.start(cfg)) {
    // Use the API.
    IgniteCache<Integer, String> cache =  client.getOrCreateCache(new CacheConfiguration<Integer, String>()
        .setName("Test")
        .setBackups(1)
    );
    cache.put(1, "foo");
    System.out.println(">>>    " + cache.get(1));
}

REST API

GridGain provides an HTTP REST client that gives you the ability to communicate with the grid over HTTP and HTTPS protocols using the REST approach.

Run the following to test your connection:

Replace the {login} and {password} with your cluster credentials. The response will contain a sessionToken.

curl "https://${connectionInfo.urls[0]}:8080/ignite?cmd=authenticate&ignite.login={login}&ignite.password={password}"

Use the sessionToken in subsequent requests to avoid authenticating every time.

curl "https://${connectionInfo.urls[0]}:8080/ignite?cmd=currentState&sessionToken={sessionToken}"

© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.

Last updated on Oct 24, 2024