Table objects, and represent the relational (primary key / foreign key) connections between their constituent tables. These specified relationships are used by Kumo to learn across multiple tables, in a way that derives optimal cross-table representations for your specified task and avoids manual feature engineering. The metadata required for graph creation is simple:
- Each constituent
Table, with a corresponding name to be used within the Graph. - The relationships between the Tables, specifying the source table (table with the foreign key), name of the foreign key, and destination table (table with the primary key corresponding to the foreign key).
How do I create a graph?
Creating a graph requires creating all of theTable objects that participate in the graph; see faq_tables for answers to frequently asked questions for table creation.
Once you have created all of your tables, you can create a Graph explicitly by passing the relevant arguments to the constructor:
How do I edit a graph?
Multiple methods exist to support adding/removing tables and edges in a graph. Concretely:add_table()adds a table to a Graphremove_table()removes a table from a Graphlink()adds an edge between two tables in a Graphunlink()removes an edge from a Graph
What does it mean to snapshot a graph?
Thesnapshot() method allows you to ingest all of the tables in a graph, so that multiple calls to train a model will use the same version of data even while the data in the source connector changes. Snapshotting a graph is also required to view that graph’s edge health statistics, which contain information about the number of matches between primary and foreign keys across all edges in the graph.