Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.ilyama.golain.io/llms.txt

Use this file to discover all available pages before exploring further.

By default, each device gets its own schema review and device-scoped mirror table (edge_mirror_{device8}_{table}). Registry coalescing lets many devices sharing the same table shape reuse one schema decision and one coalesced mirror.

​
When to use coalescing

ScenarioCoalescing mode
Heterogeneous devices, different schemas per devicenone (default)
Fleet of identical gateways syncing device_statefleet
Project-wide standard table layoutproject
Coalescing reduces operator toil: approve once, auto-approve subsequent devices with the same schema_hash.

​
How it works

  1. First device announces hash H for table telemetry_readings → registry review created.
  2. Operator approves with column actions at registry scope.
  3. Second device sends same hash H → device schema auto-approved, rows materialize to shared mirror.
  4. Physical table name pattern:
    • Project scope: edge_mirror_p{project8}_{table}
    • Fleet scope: edge_mirror_f{fleet8}_{table}

​
Policy configuration

Set coalescing mode at project level: 
PATCH /core/api/v1/projects/{project_id}/edge/policy
Body includes schema_coalescing_mode: none | project | fleet. Requires Idempotency-Key and manage-devices permission.

​
Registry HTTP routes (project scope)

MethodPathPurpose
GET/edge/registryList schema registry entries
GET/edge/registry/{registry_id}Registry entry detail
GET/edge/registry-reviewsList registry-level reviews
GET/edge/registry-reviews/{review_id}Review detail
POST/edge/registry-reviews/{review_id}/claimClaim review
POST/edge/registry-reviews/{review_id}/approveApprove with column actions
POST/edge/registry-reviews/{review_id}/rejectReject
POST/edge/registry-reviews/{review_id}/abandonAbandon
GET/edge/coalesced-mirrorsList coalesced mirrors
GET/edge/coalesced-mirrors/{mirror_id}Mirror detail
POST/edge/coalesced-mirrors/{source_table}/consolidatePhase-2 consolidation
Fleet-scoped equivalents exist under: 
/projects/{project_id}/fleets/{fleet_id}/edge/...
See API reference.

​
Consolidation

consolidate merges device-scoped mirrors into a coalesced mirror when migrating from none → project/fleet mode. Use during fleet standardization projects — coordinate with Golain support for large fleets.

​
platform-tui gap

Registry reviews and coalesced mirror management are HTTP API only today. The TUI covers per-device lineages and device-scoped schema reviews. Use curl, OpenAPI client, or automation against registry routes until TUI support lands.

​
Operator checklist (coalesced fleet)

  1. Set schema_coalescing_mode=fleet on project policy.
  2. Enroll first device → complete registry review (not just device review).
  3. Roll out identical schema to additional devices.
  4. Verify rows in coalesced mirror via GET .../coalesced-mirrors/{id}.
  5. Query with fleet-scoped filters (device_id column in mirror rows).