Crate kyma_graph 

First-class property-graph layer for kyma: wire types, the GraphProvider trait, and the synthetic schema-graph provider (catalog → property-graph).

This crate is intentionally decoupled from kyma-core: it consumes a narrow SchemaSource trait rather than the full catalog, so providers are unit-testable without a database.

Re-exports

pub use executor::GraphQueryExecutor;

pub use executor::JsonRow;

pub use executor::StoredGraphConfig;

pub use provider::GraphProvider;

pub use schema_graph::SchemaGraphProvider;

pub use stored_graph::StoredGraphProvider;

pub use source::ColumnDef;

pub use source::SchemaSource;

pub use types::Direction;

pub use types::EdgeExpansion;

pub use types::GraphNode;

pub use types::GraphPayload;

pub use types::GraphRef;

pub use types::GraphRelationship;

pub use types::GraphSchema;

pub use types::GraphStats;

pub use types::NodeMetadata;

pub use types::Props;

pub use types::SearchHits;

Modules

executor

The seam that lets the stored-graph provider run SQL over node/edge tables without kyma-graph depending on the engine. kyma-server implements this over its DataFusion query path.

provider

The provider abstraction every graph kind implements. G1a ships only SchemaGraphProvider; later phases add StoredGraphProvider behind the same trait.

schema_graph

The synthetic schema-graph: the catalog rendered as a property-graph.

source

Narrow read interface the schema-graph needs from a catalog. Keeping this tiny (3 methods) lets SchemaGraphProvider be unit-tested with a fake.

stored_graph

Stored-graph provider: serves a registered property-graph by querying its node/edge tables via a GraphQueryExecutor and shaping rows into wire types.

types

Wire types for the graph layer. These mirror the JSON contract the web Context Graph UI consumes, so field names are load-bearing.