Where gaps come from
When lineage is missing or incomplete, the cause is usually one of the following:- A service hasn’t been scanned yet, or is written in a language Gable doesn’t analyze yet. Static code analysis currently supports Java and TypeScript services.
- A detection pattern is missing. Gable’s analysis looks for declared patterns of data entering and leaving a service. If a service uses an access pattern or abstraction the analysis hasn’t been configured to recognize, the corresponding lineage won’t be detected. See Understanding the Source of Lineage Issues.
- A data store isn’t represented. Tables, streams, and files that aren’t created automatically need to be added as data store components — see Services & Data Components.
- A cross-service connection hasn’t been made. In-service lineage only chains into end-to-end lineage when cross-service edges connect the components — see Dependencies (Cross-Service Edges).
Closing gaps
To improve coverage:- Add missing components. Register data stores that participate in lineage but weren’t discovered automatically.
- Connect the graph. Create cross-service edges between components so field lineage flows end to end.
- Override incorrect or missing paths. When scanned lineage within a service is incomplete or wrong, suppress the incorrect path and create a path override — see Field Mappings & Overrides.
- Report detection gaps. If behavior didn’t change but lineage did — or lineage is missing for a pattern that should be detected — report a defect so Gable’s detection can be improved. These are typically one-time fixes tied to a specific access pattern.