Accessing the Relational Database Endpoint

Accurids includes a feature that allows data from saved searches to be exposed as a relational database endpoint.

The default port for database access, using Apache Avatica database drivers, is 8765. Currently, all database connections must be directed to the same process. In a multi-node setup, the administrator is responsible for ensuring this requirement is met.

We provide instructions on how to achieve this using Kubernetes.

Kubernetes example

First, the database port must be exported in the container specification the Accurids stateful set:

spec:
  template:
    spec:
      containers:
      - [...]
        ports:
        [...]
        - containerPort: 8765
          name: jdbc

The service maps requests to the port but ensures they are always forwarded to the same pod. In this example, this is achieved by adding a condition to the selector that restricts the name to accurids-0 (assuming accurids-0 is the name of the first pod in the setup).

apiVersion: v1
kind: Service
metadata:
  name: accurids-jdbc
  labels:
    app.kubernetes.io/instance: accurids
    app.kubernetes.io/name: accurids
spec:
  ports:
  - port: 8765
    name: jdbc
selector:
  app.kubernetes.io/instance: accurids
  app.kubernetes.io/name: accurids
  statefulset.kubernetes.io/pod-name: accurids-0