Skip to main content

​
Lineage

Mostly additive — but the new time-window filter has non-obvious traversal semantics, and the knowledge-graph renderer is replaced.

​
New FQN-based edge APIs

Additive. The UUID-based endpoints remain.
The source-scoped delete is the clean way to re-run a lineage source (dbt, OpenLineage, manual) without wiping edges contributed by other sources.

​
Batch hydration

Additive. Replaces N per-node entity GETs.
Accepts 1–200 entities, each identified by type and id only. The response groups hydrated entities by entity type. fields is applied uniformly — fields that do not apply to a given entity type are silently skipped.
Graph UIs and lineage exporters that fan out one entity GET per node should switch to a single hydrate call per page of nodes.

​
Time-window lineage

New capability with surprising semantics. Read this before using it.
The search-lineage and entity-count-lineage requests gain startTime and endTime (epoch milliseconds), matched by range overlap on edge createdAt and updatedAt. The window is applied as a hard prune during graph traversal, not as a post-filter. An out-of-window edge severs discovery of everything reachable only through it, in both directions. A node is shown only if it is reachable from the root through edges that are all in-window. Two consequences worth planning for:
  1. A single stale edge hides a whole subtree. If the edge from A → B falls outside the window, nothing downstream of B is returned even if those edges are in-window.
  2. Legacy edges always match. Edges with no timestamps match any window for backwards compatibility, so a window query over a mix of legacy and temporal data returns all legacy edges plus the in-window temporal ones. Do not read the result as a clean point-in-time snapshot until your graph is fully timestamped.
Setting endTime alone gives as-of semantics: edges that existed on or before that instant.

​
Lineage change events

Additive. Affects webhook and event-subscription consumers.
changeEventType adds entityLineageAdded, entityLineageDeleted and entityLineageUpdated. Lineage mutations previously surfaced only as generic entity updates, or not at all.
Subscriptions that filtered on entityUpdated to catch lineage changes may now see those changes arrive under the new types instead.

​
Lineage UI

Behavioural. Affects users and fork maintainers.

​
Knowledge Graph renderer replaced

Breaking for forks that import the graph components.
The AntV-G6 based knowledge graph is removed and replaced by an RDF-backed 3D Knowledge Graph tab with an Ontology mode and full-viewport expand. The components/KnowledgeGraph/** modules and NodeContextMenu are deleted; replacements live under components/OntologyExplorer/**.
The 3D graph reads from the RDF store. If RDF is disabled the tab has no data. Note also that RDF inference now defaults to off — see Applications & Automation.

​
OpenLineage & connector lineage

Additive.
Snowflake gains an opt-in access-history lineage path, dbt Cloud gains column-level lineage from compiled SQL, dbt gains semantic-layer metric ingestion with column-level lineage, and Kafka Connect creates lineage for EventRouter and RegexRouter routed topics.