Apache Ignite
Self-managed distributed in-memory platform.
Access mode: Read-only (typically)
Trino connector. Queryable via Flume’s Lakehouse. This system can be accessed both through its native protocol (for metadata introspection) and via Trino federation (for data profiling and cross-system analytical queries).
Required information
| Field | Details |
|---|---|
| Cluster endpoint | Ignite thin client endpoint or JDBC connection URL. |
| Port | Thin client: 10800. JDBC: 10800. REST API: 8080. |
| Cache / table names | Ignite caches or SQL tables to access. |
| Authentication | Ignite authentication (if enabled): username + password. SSL if configured. |
| Access level | Read-only: SELECT on SQL tables. Ignite’s thin client supports SQL queries. |
Network considerations
Self-managed only. Ignite is typically deployed inside the corporate network or VPC.
Thin client port (10800) is the primary access point for external SQL queries.
Cluster discovery: Thin client connects to one node and discovers the cluster topology. All nodes must be reachable.
Trino access: Flume’s Lakehouse queries Ignite via the Trino Ignite connector over JDBC.
Credential and auth management
Ignite authentication is disabled by default. When enabled, username + password auth.
SSL/TLS: Must be explicitly configured on the Ignite cluster. Provide keystore/truststore details if enabled.
No IAM or OAuth integration natively. Authentication is simple credential-based.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Network reachability | telnet <host> 10800 | Connected |
| Authentication + query | JDBC: SELECT 1 | Returns 1 |
| Table listing | SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES | Lists tables |
| Read test | SELECT * FROM <table> LIMIT 1 | Returns a row |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.