Glossary of terms
Definitions of the Eddytor, Delta Lake, and Arrow terms used across these docs.
Core
Eddytor - a self-hosted master-data management platform that edits and governs Delta Lake tables in your own object storage.
Delta Lake - the open table format Eddytor stores tables in (Parquet data
files + a _delta_log transaction log). Gives schema, versioning, and rollback.
Apache Arrow - the in-memory columnar format Eddytor uses to move data; also the type system for columns.
Master data - the reference/core data an organisation maintains (products, mappings, lists) - Eddytor's primary use case.
Identity & structure
Fully-qualified name (FQN) - catalog.schema.table. On self-host the catalog
is always eddytor. See FQN anatomy.
Catalog / schema / table - the three FQN parts: top-level grouping / namespace / table name.
table_id (stable UUID) - a table's permanent identity (metaData.id), unchanged
by rename/move.
Storage connection / config_id - a registered link to a bucket/container; its
config_id is referenced by object and move operations. See
Connect storage.
Governance
Column domain - a rule restricting a column's values: fixed (enum), hierarchical (parent→child), or reference (cross-table). See domains.
Constraint - a CHECK expression (SQL) evaluated on every write.
Role - viewer · editor · builder · admin (cumulative). Access is
role-only - no seats/plans. See roles & scopes.
Scope - a permission on an API key; effective access = role ∩ scopes.
Versioning & maintenance
Version - each write is a numbered Delta commit. See how versioning works.
Rollback / restore - return a table to a version (rollback) or timestamp (restore); both discard later versions. See rollback vs restore.
Optimize - compact small files. Vacuum - prune old unreferenced files (limits time-travel). See maintain.
Architecture & interfaces
Server / engine - control plane (REST/gRPC/MCP, auth, migrations) / stateless data plane that scales out. See architecture.
Flight SQL - the high-throughput Arrow read path (port 8082). See Flight SQL.
MCP - Model Context Protocol; Eddytor's /mcp endpoint lets AI clients drive
it. See MCP clients.
Magic-link / device-code - Eddytor's passwordless sign-in flows. See how sign-in works.
API key - an edd_live_… bearer credential for headless access; can be
non-expiring or given an expiry (--expires-in-minutes / expires_in:
7d·30d·90d·1y·never).
Garage - the bundled S3-compatible object store for evaluation. See bundled Garage.