MATIH Platform is in active MVP development. Documentation reflects current implementation status.
17. Kubernetes & Helm
Data Plane Charts
Query Engine

Query Engine Chart

The Query Engine routes SQL queries to the appropriate execution backend (Trino, Spark Connect, ClickHouse) based on query complexity, data size, and catalog type.


Chart Configuration

query-engine:
  enabled: true
  replicaCount: 3
 
  resources:
    requests:
      cpu: "500m"
      memory: "1Gi"
    limits:
      cpu: "2"
      memory: "4Gi"
 
  autoscaling:
    enabled: true
    minReplicas: 2
    maxReplicas: 20
    targetCPUUtilizationPercentage: 70
 
  config:
    execution:
      defaultTimeout: 300
      maxTimeout: 3600
      defaultResultLimit: 10000
      maxResultLimit: 1000000
    router:
      largeScanThresholdBytes: 107374182400  # 100GB
      complexityThreshold: 5
    cache:
      enabled: true
      ttlSeconds: 3600

Query Routing

The query engine inspects each SQL query and routes it to the optimal backend:

CriteriaBackendReason
Simple SELECT, small dataTrinoLow latency, federated SQL
Large table scans (100GB+)Spark ConnectDistributed processing
OLAP aggregationsClickHouseColumnar engine
Complex joins with ML featuresSpark ConnectDataFrame operations

Autoscaling Profile

Uses the data HPA profile for burst handling:

autoscaling:
  profile: balanced
  maxReplicas: 20  # Higher than default for query bursts